Please fix android.activity.bind(on_new_intent=callback)

[kamathln]

Currently intents don't get caught reliably . Especially when the intent launches the app.

[kamathln]

if the app was launched by an intent, we can catch it by
intent=android.mActivity.getIntent()

But if it was already running, then it is an issue.

[gorgonaut04]

I'm having this issue, and it's breaking my ability to handle facebook logins, which require receiving an intent while the app was already running. Any hints to patch this asap would be greatly appreciated so we can complete our next release :)

[inclement]

@gorgonaut04 If this worked with the old toolchain, you can look at what code it used and try to add this to the sdl2 bootstrap.

[gorgonaut04]

Good idea, will take a look.

…

On Sat, Nov 18, 2017 at 9:24 AM Alexander Taylor ***@***.***> wrote: @gorgonaut04 <https://github.com/gorgonaut04> If this worked with the old toolchain, you can look at what code it used and try to add this to the sdl2 bootstrap. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1076 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKTLx4i4GE0D9yjoNLarIibU-1_iPgwkks5s3xLfgaJpZM4OXVT4> .

[gorgonaut04]

Any hints on what could cause SDLActivity.onCreate to trigger? So far, from what I can tell using prints, the PythonActivity.onNewIntent isn't even reached when switching to the app via a redirect (using my app's scheme). Rather, SDLActivity.onCreate is triggered, causing the app to restart and keep the same process id (even though it shows the "Unfortunately, app has stopped" system popup).

[gorgonaut04]

More info: If I press the home button to leave chrome (or builtin browser, doesn't matter) before it can redirect to my app, then tap the app icon to return to the app, it resumes normally. It seems to be an issue with receiving an intent while already running(/paused), but I can't figure out why the java code wants to start the whole app over just because there was an intent.

[gorgonaut04]

yussssssss, fixed my issue simply by adding android:launchMode="singleTask" to the main <activity> tag in the manifest template (AndroidManifest.tmpl.xml). Current users can apply this hotfix to {app-directory}/.buildozer/android/platform/build/dists/barly/templates/AndroidManifest.tmpl.xml