the app was built for an older version of android.... install anyway

[g1i1U]

Checklist

• I have searched the issue tracker for open issues that relate to the same problem, before opening a new one.
• This issue only relates to a single bug. I will open new issues for any other problems.

Describe the bug

why when i try to install the created fyne/go apk on my android it says :
"the app was built for an older version of android" install anyway

any fix here

How to reproduce

fyne package -os android -appID com.g1i1u.goscanner -icon icon.png

Screenshots

No response

Example code

Fyne version

v2.5.2

Go compiler version

go1.22.2 darwin/amd64

Operating system and version

macos ventura 13.5

Additional Information

No response

[andydotxyz]

My understanding is that this is Google Play Protect wanting us to drop support for older devices.
The apps are not "built for an older android" - they target the latest API, however it does support very old versions.

So to make this go away we would have to drop support for a load of OS versions due to Googles desire to drop that support.

Should we?

[hkparker]

Would it be possible to easily opt-in or opt-out of this support? So that those who are concerned about this warning message can drop it, without losing the ability for those who it matters to. Not sure if this is just something declared in the manifest or more involved, but I'm imagining a fyne package flag to drop older version support (or, if the default is to drop it, a flag to add it).

[andydotxyz]

Unfortunately the minSDK defines what "shims" or support adapters are compiled in on the Android size. This is why we hard-code it because changing that as developers specify would (could?) change how Fyne functions and possibly break functionality.
To switch between them would need alterations in the codebase as well as at the manifest level to compensate.

[ppxl]

Unfortunately the minSDK defines what "shims" or support adapters are compiled in on the Android size. This is why we hard-code it because changing that as developers specify would (could?) change how Fyne functions and possibly break functionality. To switch between them would need alterations in the codebase as well as at the manifest level to compensate.

Funny that this issue is currently being discussed as I have a similar behaviour as my app will be completely blocked

Both copying on the Android FS and installing from there as well as installing it via adb will be allowed with a message á la: Insecure App blocked resp.
adb: failed to install learning_day_go_ui_with_fyne.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE: Install not allowed for file:///data/app/vmdl934522783.tmp]

Now that some hardcoding was discussed here:
Is there something I can hack my way through so I can manage to run my silly demo app on the phone?

Edit: I should mention my Galaxy phone runs on Android 14, the app was packaged with fyne 2.5.2

Edit2: The adb switch --bypass-low-target-sdk-block was out of luck as well

[ppxl]

Unfortunately the minSDK defines what "shims" or support adapters are compiled in on the Android size. This is why we hard-code it because changing that as developers specify would (could?) change how Fyne functions and possibly break functionality. To switch between them would need alterations in the codebase as well as at the manifest level to compensate.

Funny that this issue is currently being discussed as I have a similar behaviour as my app will be completely blocked

Both copying on the Android FS and installing from there as well as installing it via adb will be allowed with a message á la: Insecure App blocked resp. adb: failed to install learning_day_go_ui_with_fyne.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE: Install not allowed for file:///data/app/vmdl934522783.tmp]

Now that some hardcoding was discussed here: Is there something I can hack my way through so I can manage to run my silly demo app on the phone?

Edit: I should mention my Galaxy phone runs on Android 14, the app was packaged with fyne 2.5.2

Edit2: The adb switch --bypass-low-target-sdk-block was out of luck as well

The Google Play protect screen did offer some help which I didn't recognized as that. It is possible to generally disable app scanning inside the Google Play app > ⚙️ > "Scan apps with Play Protect"¹ > switch to off
I know, doing so this is generally considered unsecure. I hope I will remember to switch back once I am finished.

Anyway, thanks for reading.

¹: My Android is in german so I hope the translation will fit, YMMV

[andydotxyz]

@ppxl that is a different issue - if you want to discuss it please open a new ticket. The version warning is not a blockage and apps can be installed or released to the store with the current settings.

A complete block is not something we have seen before and may relate to your code or other settings in your project. As it's an Android specific error googling may turn up related posts from native developers.

[ppxl]

@ppxl that is a different issue - if you want to discuss it please open a new ticket. The version warning is not a blockage and apps can be installed or released to the store with the current settings.

A complete block is not something we have seen before and may relate to your code or other settings in your project. As it's an Android specific error googling may turn up related posts from native developers.

I see. I think I will leave it at that for now. Thanks for your work and time 👍