Crash in Android 15

[Siavash Rahnama]

Since Android 15, app service doesn't run any flows, and opening the app causes an infinite launch/crash loop.

Tired: clear app data, uninstall, reinstall, stable and beta

[Henrik "The Developer" Lindqvist]

Not good. I can't reproduce any such issue with the stable v1.42.6 in the Android 15 emulator.

Ensure to click OK in any "submit crash report" dialog, then i might be able to see it in the Google Play console.

[Siavash Rahnama]

So the problem isn't yet known

This is a screen record of the app trying to start. App data fully cleared 

version 1.42.6

com.llamalab.automate

Android 15 beta

AP31.240322.027

Google Pixel 7

https://youtube.com/shorts/jenDbSll2nk?si=kHzctKotkG0il525

[Siavash Rahnama]

Correction 

https://youtu.be/_bF5k2KKO_w?si=xLK8MjoMw95A9mmz

[Henrik "The Developer" Lindqvist]

Odd, seems to be some graphical issue.

Probably an Android bug since the system should show a slash screen first, which is does before the before the app has even started.

[Siavash Rahnama]

I also sent you the logcat of the event via private message. It might be helpful

[Henrik "The Developer" Lindqvist]

That would be great. Sadly, i haven't receive any such message, please email me the log to in...@llamalab.com instead.

[Henrik "The Developer" Lindqvist]

Thanks for the log. The last logged error message is truncated so its difficult to tell if that's the cause, but it seems to be to originate from some internal Android component called "ReviewPermissionsFragment".

That i can't do much about, but a workaround might be to grant some or all permission to Automate in system Apps settings.

PS. Never post a system log on the public forum as they might include sensitive information. Post deleted.

On Tuesday, May 7, 2024 at 1:37:20 AM UTC+2 sia...@gmail.com wrote:

[Siavash Rahnama]

Well. Since you didn't receive private message I had to post it here. Your email address was also redacted by the forum.

Anyway, apart from the permission manager (I tried granting every normal and additional permission after checking the logcat and it didn't help), what caused the fatal error was an exception with background activity start blockage, and finally exiting with error code 102

This part doesn't seem so sensitive:

05-06 02:53:38.860 1622 2646 E ActivityTaskManager: Background activity launch blocked! [callingPackage: com.android.settings; callingPackageTargetSdk: 10000; callingUid: 1000; callingPid: -1; appSwitchState: 2; callingUidHasAnyVisibleWindow: true; callingUidProcState: PERSISTENT; isCallingUidPersistentSystemProcess: true; forcedBalByPiSender: BSP.NONE; intent: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=com.llamalab.automate cmp=com.llamalab.automate/.FlowListActivity }; callerApp: null; balAllowedByPiCreator: BSP.NONE; balAllowedByPiCreatorWithHardening: BSP.NONE; resultIfPiCreatorAllowsBal: BAL_ALLOW_ALLOWLISTED_UID; hasRealCaller: true; isCallForResult: false; isPendingIntent: true; autoOptInReason: null; realCallingPackage: com.google.android.permissioncontroller; realCallingPackageTargetSdk: 10000; realCallingUid: 10223; realCallingPid: 3933; realCallingUidHasAnyVisibleWindow: true; realCallingUidProcState: TOP; isRealCallingUidPersistentSystemProcess: false; originatingPendingIntent: PendingIntentRecord{5d2f070 com.android.settings startActivity}; realCallerApp: ProcessRecord{756b442 3933:com.google.android.permissioncontroller/u0a223}; realInVisibleTask: true; balAllowedByPiSender: BSP.ALLOW_FGS; resultIfPiSenderAllowsBal: BAL_ALLOW_VISIBLE_WINDOW]

05-06 02:53:38.861 1622 2646 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=com.llamalab.automate cmp=com.llamalab.automate/.FlowListActivity} with LAUNCH_MULTIPLE from uid 1000 (realCallingUid=10223) (BAL_BLOCK) result code=102

[Henrik "The Developer" Lindqvist]

Another thing to try, that involves permission, is to uninstall all Automate permission extension apps if you have any installed, see:

https://llamalab.com/automate/doc/extensions.html

Also, if possible, in system Apps settings, Special app access, Display over other apps, Show system apps (menu), enable if for System UI and Settings if present.

Beyond that, i can't come up with any more workarounds. I suggest you report the issue to Google, and hope that they fix it, see:

https://developer.android.com/about/versions/15/feedback#feedback-app

[Siavash Rahnama]

Bingo!

Connectivity permissions it was!

Thanks a lot 

[Henrik "The Developer" Lindqvist]

I've reported it to Google, please star: https://issuetracker.google.com/issues/339481288

[Siavash Rahnama]

Done