2
Solved

Unable to launch apps in Android 13

I have a Galaxy S20 Ultra 5G (not rooted). Previously on Android 12. Just upgraded to Android 13, on any tasks to launch apps, I get the error "Launch App: failed to launch com.sec.android.app.xxx". It doesn't read like a permission issue. Run Log just shows "err" on the launch app task.

I've tried re-setting cache from recovery menu.  Also tried wiping data/cache for the tasker app.

Any suggestions?

4 replies

RR

Sorry joining the conversation, your latest link not showing error anymore but didn't open specific setting. Only "home" of setting opened 

LF

Exactly my experience.

LF

Same problem here after upgrading to Android 13 in a Galaxy Note 10 Lite.

The LaunchApp does not work (Error Code 1) if I add Data, but without Data the app opens normally without error.

Can you give me an example of app and data that is happening with? Thanks

RR

yes its happen to me too, only when launch specific settings, in example "more connections setting". im on Fold4 android 13

Hi. Maybe it's that specific app? Does it work if you launch YouTube for example?

LF

I am commenting here because I cannot comment on your question to my post.
The error happens with, say, YouTube, and Data being the string "linha" (with or without quotes). Yet, with Firefox as app it works... Thanks!

Hhmm, what happens when you do that? do you get an error? 

Does it work if you use the "Browse URL" action instead?

LF

Yes. Tasker shows a notification popup:

            Tasker action error ...
            Action: Launch App
            ...
            Error code: 1. 

If I run the task from Tasker, I see the error in Launch App:

     E Launch App: failed to launch <A class name>
     E result: stop task (error)
     E Error: 1

I haven't seen no problems with any other action, in particular, Browse URL works fine. But not with every app: YouTube gives error, Firefox doesn't.

Can you please export your task's description (not xml) (the one that uses Browse URL with YouTube and shows an error) so I can take a look? Long-click the task in Tasker->export description Thanks in advance

LF

Sorry, maybe I wasn't clear enough. Browse URL works fine. What does not work is Launch App with YouTube if you add Data. Launch App with Firefox works, with or without Data.

Anyway, this is the description (only 1 action):

Task: 409
A1: Launch App [ Package/App Name: YouTube Data: linha=409 ]

I see. What exactly were you trying to do with that "linha" data? The "data" field should be an URI, and that's probably why it's erroring out...

LF

I discovered the error not with YouTube as app, but as my own app that requires a string as data (and then processed by it). This crash appeared only after upgrading to Android 13. I have been using this for years... 

Anyway, Launch App is giving the same error with Data also being https://youtu.be/izY229ElAgw or izY229ElAgw

Do you know some Data URL for YouTube app that should not give an error?

Thank you! I think I finally figured it out and fixed it :)

Can you please try this version? https://drive.google.com/file/d/19w0kkEle9oinGusDHMe-1f1u6_xuuifD/view?usp=sharing

LF

Your new version works with YouTube as app. But not with my own app. Moreover, I am getting tons of "permission denied", so for my uses this version is worse than the stable one. See this:

Hhmm, what Android version are you using? Thanks

LF

The problem only began after upgrading to Android 13 (in a Samsung Note 10 Lite) .

Ok, does it work now?

Can you please try this version? https://drive.google.com/file/d/19w0kkEle9oinGusDHMe-1f1u6_xuuifD/view?usp=sharing

LF

Tasker does not give error now, the app opens, but the Data field is not read (correctly?) by the app. It's like Tasker ignores the Data field.

Exactly like Raditya Rinaldi described.

LF

Using Android Studio I checked that your new Tasker version simply does not send any Data when Launching App: getIntent().getData() is null. That's why the app is launched, but not working as pre Android 13.

Can you please post a link to the stable version for me to roll back? Your last version gives tons of errors.

Thanks!

You can get the stable version here: https://tasker.joaoapps.com/releases/playstore/Tasker.6.0.10.apk

However I'd really like to know the ton of errors you're getting. Can you clarify?

About the Launch App error, does it work like you expected it to in the version above?

LF

> You can get the stable version here: https://tasker.joaoapps.com/releases/playstore/Tasker.6.0.10.apk 

I cannot install this apk. It gives me:

"Package appears to be invalid".

> However I'd really like to know the ton of errors you're getting. Can you clarify? 

I am periodically getting the error in the screenshot I posted above (Permission denial).

> About the Launch App error, does it work like you expected it to in the version above?

I cannot install the version above.

With the stable version that I had before you asked me to test, I got an error, as described originally.

With the beta you asked me to test, Tasker is not sending any data to the Intent (null). So the problem is not fixed, and I am getting new Tasker errors periodically as shown in the screenshot. So it is working worse than the original version that I had.

Thanks,

L.

With the beta I sent you it's not sending data because I added a fallback so that the app is opened without data if it fails to open with data. 

The changes arise from a change in how Android handles app opening which is more strict on recent Android versions. Maybe it's best to simply error out with an error saying that the data can't be used with that activity instead of opening the app without data?

About the error you mentioned, I fixed it.

Can you please try this version? https://drive.google.com/file/d/19w0kkEle9oinGusDHMe-1f1u6_xuuifD/view?usp=sharing

Hope this helps.

LF

> With the beta I sent you it's not sending data because I added a fallback so that the app is opened without data if it fails to open with data.

I see. That explains what is happening and is consistent to what I realized with Android Studio.

> The changes arise from a change in how Android handles app opening which is more strict on recent Android versions.

Oh, boy, Android breaking Android once again... Android is the perfect nightmare for a dev.

How can be this solved? Is there something that the app developer can do (Manifest permissions?) to "accept" the data?

> Maybe it's best to simply error out with an error saying that the data can't be used with that activity instead of opening the app without data?

I think so, yes. Which kind of error Tasker actually sees when trying to open an Intent with data that fails?

Again, is this a permission issue in the app side?

>  About the error you mentioned, I fixed it.  Can you please try this version? https://drive.google.com/file/d/19w0kkEle9oinGusDHMe-1f1u6_xuuifD/view?usp=sharing 

I installed it. If error persists I will report back.

> Hope this helps.

Always!! Love Tasker.   ;o)

Ok, I tried something else now. Can you please try with this version? https://drive.google.com/open?id=19w0kkEle9oinGusDHMe-1f1u6_xuuifD&authuser=joaomgcd%40gmail.com&usp=drive_fs

LF

With this version I get an error Launching app with Data, but a different one: Activity not found. See:

07.45.59/Utils startActivityWrapper: activity not found 07.45.59/Log startActivityWrapper action: android.intent.action.MAIN 07.45.59/Log startActivityWrapper pkg: null 07.45.59/Log startActivityWrapper cpkg: com.floritfoto.apps.riobas 07.45.59/Log startActivityWrapper ccls: com.floritfoto.apps.riobas.BusMap 07.45.59/Log startActivityWrapper flags: 805306372 07.45.59/Utils startActivityWrapper: activity not found 07.45.59/Log startActivityWrapper action: null 07.45.59/Log startActivityWrapper pkg: null 07.45.59/Log startActivityWrapper cpkg: com.floritfoto.apps.riobas 07.45.59/Log startActivityWrapper ccls: com.floritfoto.apps.riobas.BusMap 07.45.59/Log startActivityWrapper flags: 805306372 07.45.59/E Launch App: failed to launch com.floritfoto.apps.riobas.BusMap. 07.45.59/E result: stop task (error) 07.45.59/E Error: 1 07.45.59/MacroEdit action finished exeID 1 action no 2 code 20 status: Err next 2

Can you please try with YouTube and see if that works?

In later Android versions you have to declare which type of data your activity is able to get in the app manifest and unfortunately it seems like the app you're trying it with doesn't do that.

LF

YouTube works now, and accepts the Data!  So it seems you fixed the problem. Now I need to update my app to Android 13 to get the Data correctly in the Intent filter.

Thanks!!!

Great! :) Glad it works!!

Topic is closed for comments