Dear Yoeden,
You've written a very nice package, thank you very much first of all.
The problem of current build which is available on pub.dev is in hardware type in manifest file of the package.
I mean this: <uses-feature android:name="android.hardware.type.watch"/>
ISSUE:
Since we develop app only for WearOS standalone or not - doesn't matter, we have no problem here.
In Google Play we just creating a new track for WearOS and publishing APK there (for WearOS market)
When we've done APK of Main/Companion App for Android with support of WearOS capability, we can't publish it
as usually because of this error from Google Play Market:
This APK or bundle requires the Wear OS system feature android.hardware.type.watch. To publish this release on the current track, remove
I don't know how to solve this conflict(maybe you may create 2 type libs or somehow using another way),
but I found a workaround which is worked for me. I really hope it will help someone to publish their great apps.
WORKAROUND:
After we build app for WearOS only we should comment this
in AndroidManifest.xml of this package. (And also in your own manifest)
UPD:
I think just better to remove this from package manifest and just let user manage this by himself.
In documentation just tell setup this capability in their manifests.
Dear Yoeden, You've written a very nice package, thank you very much first of all.
The problem of current build which is available on pub.dev is in hardware type in manifest file of the package. I mean this:
<uses-feature android:name="android.hardware.type.watch"/>
ISSUE:
Since we develop app only for WearOS standalone or not - doesn't matter, we have no problem here. In Google Play we just creating a new track for WearOS and publishing APK there (for WearOS market)
When we've done APK of Main/Companion App for Android with support of WearOS capability, we can't publish it as usually because of this error from Google Play Market:
This APK or bundle requires the Wear OS system feature android.hardware.type.watch. To publish this release on the current track, remove
I don't know how to solve this conflict(maybe you may create 2 type libs or somehow using another way), but I found a workaround which is worked for me. I really hope it will help someone to publish their great apps.
WORKAROUND:
After we build app for WearOS only we should comment this in AndroidManifest.xml of this package. (And also in your own manifest)
<uses-feature android:name="android.hardware.type.watch"/>
and build app for Android only or Android with capability of WearOS. Thats 100% works for me.
Of course we should check-up calls of send/listen for exceptions in case user doesn't have WearOS API installed on device.
Thank you in advance!