So, what you need when releasing/deploying is really 2 BUNDLES: 1 for Android (phones) and 1 for Wear OS - instead of 1 bundle with 2 modules.Īnd you can relax about making those "bundles", in contrast with making APKs sounds more scary than it is. Well, NO! By configuration they just mean different screen sizes, density, etc.
it would also imply, in my view, that Wear OS is one such configuration, so should consist in a module inside 1 project. Now I think I know what your problem is, because I had it before, and the Android documentation doesn't clearly remove the ambiguity when saying that a bundle caters to different configurations, etc. Nothing helps - got the same answer from google support (to add the to the phone manifest ) - but then - google play console do not allow me to upload this bundle I have tried all solutions from the following:
Upload a Wear OS app bundle or APK to a test track" ?īut the google docs say no way - they say to upload the bundle only. Maybe I should upload the wearos APK - it is written " WearOS APK was also created in the release folder. On my release folder I have a new bundle which is 2 Mega more then before - looks like it have the wearOS packed inside. They told me they will return me an email. I have contacted support chat - they do not know. I have upload the bundle to opt in from the Advanced tab - wear OS - nothing changed. The paired phone behind, your watch app can't get location data through aĬonnected device.How to prepare my app for the wearOS module opt in?ĪpplicationId "" If a user goes jogging with a watch that lacks a built-in GPS sensor, and leaves Note: When creating a LocationRequest, it's important to consider batchingīecause it can consume less battery and give a more accurate location, depending User's location, see Request location updates. The FLP automatically uses location data from the phone if the watch lacks a GPSįor information about requesting location updates and continuously tracking a Location data for watches paired to iPhones. Your app is a workout or exercise app that needs to track location data over.You want data from other sensors, or are likely to want data from other.You want location continuously, but don’t need the location history.You want location data in the moment but not continuously, such as marking the.There are a couple of ways to provide location data to a Wear OS app. Location data when a watch without a sensor becomes disconnected from a phone. When possible, to conserve battery you should ask for location no moreĪs described in the following sections, your app needs to handle the loss of To reduce the negative impact of location data acquisition on battery life, So even without a GPS sensor in the watch, you can still System will get location from either the phone or watch using the most
When you request location data in a watch app, the Some watches have a built-in GPS sensor that retrieves location data without Or provide glanceable cues about users' surroundings.įor more information, see Build location-aware apps. As examples, you can buildĪpps that give users real-time updates on their distance, speed, and direction, That record, report, and respond to user location. A watch's small, glanceable form factor makes Wear OS an ideal platform for apps