Camera requirements in SDK Manifest are mandatory

[isles1217]

Describe the bug When preparing a release for OSM on Android, I discovered that the Klarna SDK declares a camera requirement that differs from our app’s requirements that is NOT mentioned in the documentation. Is there a way to make these features optional in your SDK? Releasing our app with the Klarna SDK as is will result in dropping support for devices without cameras.

From the Klarna SDK’s AndroidManifest.xml file:

    <uses-permission android:name="android.permission.CAMERA" />
    <uses-permission android:name="android.permission.FLASHLIGHT" />
    <uses-feature android:name="android.hardware.camera" />
    <uses-feature android:name="android.hardware.camera.autofocus" />

Expected behavior These camera requirements can be made optional with a required=false tag, ie:

    <uses-permission android:name="android.permission.CAMERA" />
    <uses-permission android:name="android.permission.FLASHLIGHT" />
    <uses-feature android:name="android.hardware.camera" android:required="false" />
    <uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
    (something similar for the flashlight permission)

Screenshots

Device and version:

• Device: Android
• Klarna In-App SDK version: 2.0.42

Merchant Name Babylist

Impact Level Blocking release, dropping supported devices

Additional context

[NMGuner]

Hi @isles1217, thanks for the feedback and notifying us about this issue. You have a valid point there as these features are optional and shouldn't block you from releasing your app to those devices. We started taking a look into this and hopefully will release a new version with the fix as soon as possible.

[isles1217]

Thanks a lot, @NMGuner !

[NMGuner]

Happy to notify that we released a new version(2.0.44) with optional requirements and checks in the SDK to not run into issues during runtime. I will mark this issue as resolved but feel free to update us if you keep experiencing this problem.