Skip to content

Can no longer start engine on Android #680

Answered by cdigit
cdigit asked this question in Q&A
Discussion options

You must be logged in to vote

The problem is currently resolved as a stated earlier, and it wasn't a miniaudio issue.
I think the problem has to do with how certain Android targetSdkVersions allow runtime permissions or not. I think my permissions were being ignored because the app was installed with a new Sdk version over a previous version of the app where the user prompt for permissions was set many months ago (on multiple devices) and Android did not re-prompt for permissions until I manually changed the SDK version and did a clean build and install. I also think this has something to do with it too: https://stackoverflow.com/questions/45163008/android-failed-to-finalize-session-26-new-target-sdk-22-doesnt-support…

Replies: 3 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@cdigit
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
3 replies
@cdigit
Comment options

@mackron
Comment options

@cdigit
Comment options

Answer selected by cdigit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants