APP - different ANDROID versions, different behavior

[AlexanderMaydorf]

AIR SDK 50.2.4.3
ANIMATE 2024
ANDROID SDK 33 / BUILD TOOLS 33

ANDROID 11

After displaying the SYSTEM authorization screen - and switching to "ON" - APP restarts - but "installing unknown apps" is granted.

ANDROID 13

SYSTEM authorization screen is showing up, but app runs and goes forwards without waiting or checking response.

[marchbold]

Can you elaborate some more on exactly what you are doing? Some code can help demonstrate the issue.

[AlexanderMaydorf]

if ( PackageManager.isSupported){
  if (!PackageManager.service.canRequestApplicationInstalls){
    PackageManager.service.showManageUnknownAppSourcesSettings();
  }
}

That's it.

ANDROID 11 tablet:

System screen will show up - APP is doing nothing
after switching permission for "install unknown apps" ON - app restarts

ANDOID 13 tablet:

System screen will show up - APP is going on (because I do this at initialisation -next steps will executed
after switching permission for "install unknown apps" ON - app is still running...

---

I guess the "restart" is not "normal".
But what about the "running in background" while user gives permission ... is there no listener for this?

When I grant total file access - a similar looking system screen show up - but here AIR is firing an event, if the user gives permission...

[marchbold]

App restarting after changing certain permissions is normal and is controlled by the android system so can be different between versions of android.

Regarding a callback, as far as I know this particularly change doesn't have a callback. You would have to use normal app activation events after calling it to check the permission again.

This is one of those non standard permissions that sits outside the normal permissions flow.

[AlexanderMaydorf]

Ah, okay. I was think something like that. I checked LogCat – and there is nothing really interesting to find. But it’ still bad ;-) I was hope it works like the file permission to get full access of the file system. This works so nice ;-) I decided now, to stop the app – after requesting the permission and tell before, that the user has to restart it. This is not perfect, but so – I have the same solution for any version. Thank you! (GREAT WORK!) Von: Michael ***@***.***> Gesendet: Montag, 29. Januar 2024 23:41 An: distriqt/ANE-PackageManager ***@***.***> Cc: AlexanderMaydorf ***@***.***>; Author ***@***.***> Betreff: Re: [distriqt/ANE-PackageManager] APP - different ANDROID versions, different behavior (Issue #11) App restarting after changing certain permissions is normal and is controlled by the android system so can be different between versions of android. Regarding a callback, as far as I know this particularly change doesn't have a callback. You would have to use normal app activation events after calling it to check the permission again. This is one of those non standard permissions that sits outside the normal permissions flow. — Reply to this email directly, view it on GitHub <#11 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEM7FFURP2ZYEAOQZ6P4CITYRAQP5AVCNFSM6AAAAABCOEOIEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVG4YDCMJRG4> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AEM7FFQSTBW5QLV5BGCNGNDYRAQP5A5CNFSM6AAAAABCOEOIEOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTSF5DX2.gif> Message ID: ***@***.*** ***@***.***> >