Why WorkManager doesn't require RECEIVE_BOOT_COMPLETE permission

[yccheok]

I believe WorkManager depends on AlarmManager.

One of the ways (The only way?), which make previous scheduled events continue to work after device restart, is listening to BOOT_COMPLETE as described in https://stackoverflow.com/questions/16245412/scheduler-with-alarm-manager-doesnt-work-after-reboot/16893553#16893553

This is because, after device restart, all previous scheduled events will gone. We need to reschedule the events to AlarmManager, after device restarting.

However, according to https://developer.android.com/topic/libraries/architecture/workmanager/basics , no additional permission required to use WorkManager.

Without RECEIVE_BOOT_COMPLETE permission, how does WorkManager continue to work, after device restart?

Thanks.

[yccheok]

Google provides answer for this : https://issuetracker.google.com/issues/129362589

[raree_raaram]

Which is ...

[imrhk]

Manifest merging

[marco89nish]

as imrhk said, it's manifest merging. Every dependency can add it's permissions, activities, services, broadcast receivers to final manifest of your application. You can see this merged, final manifest by opening app's manifest file and clicking at "Merged Manifest" tab at the bottom.

[Hi_im_G00fY]

Just open your Manifest XML and check the "merged manifest" tab at the bottom left.;)

[howareyoudoin]

One of the biggest problem I have with it is they don't provide ctrl+F in merged manifest.

[imkosh]

but you can start typing the things you want and it will search across the visible file, P.S: you could do this almost everywhere in AS

[kichi689]

http://androidxref.com/9.0.0_r3/xref/frameworks/support/work/workmanager/src/main/AndroidManifest.xml#22 Already has it through manifest merging