IssueTracker

Due to the pattern I am noticing when researching the other reports of this bug, I have a feeling this ticket will be closed as "Won't Fix (Obsolete)" when it clearly is not. I can confirm that this issue exists in Android 10, so unless Android 10 is obsolete, and this issue is not reproducible in the current Android versions, I would hope to see this get fixed before the Android 11 release.

Tickets reporting this issue but closed:

• https://issuetracker.google.com/u/1/issues/124618498
• https://issuetracker.google.com/u/1/issues/138423608
• https://issuetracker.google.com/u/1/issues/37324352
• https://issuetracker.google.com/u/1/issues/37137009

This also very likely affects the new Jetpack App Startup library which heavily relies on ContentProviders.

Given those (Firebase, Jetpack App Startup) are official Google products I am wondering whether this means that Android Backup will be sunsetted soon or otherwise would need extensive changes to its implementation (which would likely be hard to roll out to older devices as AFAIK it's shipped with the OS). Would be great to get some official statement here so that we have enough time to migrate away our apps from Android Backup to some other backup service.

It's been a bit over a year since I reported this issue, and I have a feeling that it hasn't been resolved in Android 12. Nudging this ticket a bit to hopefully get some eyes on this, especially since Hilt seems to require the Application class to be extended.

Awesome! Can you link the commit for the fix? Thank you.

If you want to work-around this issue in case user is starting the Main Activity to your app while it is in restricted mode thus will crash at some point, you can do this in your startup Activity to force kill the process so it starts next time in non-restricted mode:

	@Override
	public void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);

		if(!(getApplication() instanceof MyCoolApplicationSubClass)) {
			// app is in restricted mode, kill it
			new Handler().post(() -> System.exit(0));
			finish();
			return ;
		}
                // else start normally
        }

A fix for apps restarting in restricted mode if they crash during backup was merged in T. Folks still reporting this issue in T+ Android versions, can you confirm if you are seeing your app being restarted in restricted mode, preventing users from using the app?

Please share the information requested in comment#12 to proceed further.

We've observed similar crash reports in play console only on T+:

1. android:allowBackup="true" in application manifest
2. A custom application class, initializing some global static instances on created
3. MainActivity tries to access these global instances on created, assuming they've already been initialized, leading to a crash

Regarding specific data by OEM/device, this crash commonly occurs on T+, including Google Pixel. HONOR devices seem to be more prone to this issue, but users from other OEMs (Samsung, OPPO) reported a higher frequency (>5 events per user)