I saw this. My interpretation is that Samsung changed how WFS structures the manifest file so that it complies with the latest info in the WFF guide. WFS creates the manifest itself; it doesn’t let users tweak it.
If you really need control over the manifest, you could extract the watchface.xml produced by WFS and create a WFF project using it. But you’d then need to rebuild the project outside of WFS (eg, using gradle).
@neeldedkawala you can create a Android App Bundle (aab) and extract it. You can access the manifest file from there.
@imrulanwar836 How can I extract the aab file, would that be encrypted and then how can I import that into android studio as project to update manifest in there
@neeldedkawala Are you sure you really want to do this? What change to the manifest do you need to make?
I want to change this line : "uses-feature android:name=“android.hardware.type.watch”
in the manifest with this line : uses-feature android:name=“android.hardware.type.watch”
android:required=“false”
@neeldedkawala rename tha file like this:
something.aab → somthing.zip
extract it. Make your changes. I would suggest making a copy of your work first.
yes it would be better to make a copy of the project first.
This still seems like a strange requirement. It sounds like developing a watchface that doesn’t require a watch. I’m wondering if the apparent need is attributable to trying to publish something to the wrong channel in the Google Play Console, or not completing the Wear OS stuff.