Hi @Pearl , sorry to bother you! I'm posting this answer to help others who might encounter the same issue.
Thanks for sharing the update that creating a new project and adjusting the Target SDK versions to 34 and Minimum SDK to 26 resolved the issue.
The reason for this solution is because some of the project configuration and manifest settings in your original MAUI project might be likely outdated or inconsistent. This can lead to compatibility problems where the APK installs fine on some devices but fails on others, especially newer Android versions that enforce stricter requirements.
By creating a fresh MAUI project, you essentially reset the configuration to align with the latest tooling defaults. That new template automatically:
- Configured the Target SDK to 34 (which is required for publishing on Android 14 and recommended by Google).
- Set the Minimum SDK to 26, ensuring backward compatibility with supported devices.
- Cleaned up any legacy or incorrect settings that could interfere with APK signing and installation.
When you migrated your code into this clean project, you carried over only the logic/files and not the outdated metadata. As a result, the APK built from the new project was signed and packaged in a way that matched Android’s current requirements, so installation succeeded across all devices.
I'm glad that you finally solved your issue. If my answer explains your workaround correctly, feel free to interact with the system accordingly!
Thank you!