Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataDog crashing with directBootAware-"true" attribute #1116

Closed
BBaleilevuka opened this issue Oct 31, 2022 · 4 comments · Fixed by #1209
Closed

DataDog crashing with directBootAware-"true" attribute #1116

BBaleilevuka opened this issue Oct 31, 2022 · 4 comments · Fixed by #1209
Labels
bug Something isn't working waiting-for-info Waiting for additional info from reporter

Comments

@BBaleilevuka
Copy link

BBaleilevuka commented Oct 31, 2022

direct_boot_aware_work_manager_crash.log
Thanks for taking the time for reporting an issue!

Describe what happened

  • When using DataDog Log reporting in a directBootAware="true" application, the WorkManager inside the DataDog SDK isn't permitted to run before the device in unlocked.
  • Our Application is running on boot-up and is used on the lock-screen to unlock the device.

Steps to reproduce the issue:

  • Create an Android application.
  • In the manifest file add the android:directBootAware="true" flag
  • Run the application

Describe what you expected:

  • Datadog can be used within a directBootAware application without crashing.

Additional context

  • Android OS version: AOSP 11(non-gms)
  • Device Model: RealWear Navigator 500
  • Datadog SDK version: 1.14.1
  • Versions of any other relevant dependencies (OkHttp, …): androidx.appcompat:appcompat:1.3.0
@BBaleilevuka BBaleilevuka added the bug Something isn't working label Oct 31, 2022
@xgouchet
Copy link
Member

xgouchet commented Nov 2, 2022

Hi @BBaleilevuka , and thanks for reporting this issue. We're going to take a look at this and will come back to you as soon as possible.

@xgouchet
Copy link
Member

xgouchet commented Nov 2, 2022

HI @BBaleilevuka ,
This issue was reported a while ago but we never managed to reproduce it on our side. It seems that adding the android:directBootAware="true" flag to an application is not enough to make the application crash, do you have more precise steps to reproduce the crash?

@xgouchet xgouchet added the waiting-for-info Waiting for additional info from reporter label Nov 2, 2022
@BBaleilevuka
Copy link
Author

Hey @xgouchet,

Thanks a lot for responding. I will attempt to get an example android project up and repo steps as soon as I can.

In the mean time, the main step which is important is having a full-disk encrypted device or file-base encrypted device, and then run an application that starts before the device is unlocked: https://developer.android.com/training/articles/direct-boot#dpm

I will get back to your with a demo app and repro steps asap.

Again, thank you very much @xgouchet

@xgouchet
Copy link
Member

xgouchet commented Nov 4, 2022

Thanks @BBaleilevuka , having the device encrypted is the key information I was missing. We'll take a look at this issue and come back to you when we have more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working waiting-for-info Waiting for additional info from reporter
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants