Very Slow Release and Screenshots for Versa Lite

[Credelius]

@JonFitbit 

The release process is very slow. It took 10 days for the last review, and the app was still rejected, because screenshots for Versa Lite were not provided.

Where should I put screenshots for Versa Lite? There are only two tabs: Ionic and Versa (see the pic below).

The most frustrating part of all that - the app was broken, because of SDK changes that were not backward compatible, and now I can't release the new version because of very obscure reasons. As a result, users can't use the app for the last two weeks. Is there any way to speed up the process?

BTW, no app store except Fitbit requires separate screenshots for different models. This is something that Fitbit needs to re-consider. When I do screenshots for different models, I just resize them, but so could do your platform. What's the point here?

PS. I've removed Versa Lite from supported models and submitted the new version for the review again. I hope, it'll help to release fast. 

  

[JonFitbit]

The reviewer team size has just increased to deal with the higher volume, thanks for your patience.

The Versa Lite tab appears when you add a build with support for Versa Lite.

What's the UUID of the app? I can see about getting it express reviewed.

[Credelius]

@JonFitbit thanks for the quick response. In regard of screenshot for Versa Lite, I did check Build for Versa Lite check box in Studio, but the upload tab didn't show up, so I had to re-build the app again after unchecking Versa Lite box.

The team has accepted the release this time, but I don't have Versa Lite support anymore. Looks like a bug in your release dashboard. 

[JonFitbit]

The Versa Lite tab appears after you upload the build, then you add the screenshots. It's not really obvious unfortunately.

[Credelius]

@JonFitbit 

See two pictures below. The app is built with Versa Lite support. The binary is uploaded, but Versa Lite tab is not present in uploads. What button do I need to press to get that tab?

 

[JonFitbit · Accepted solution]

At that point, it's not actually uploaded the build. You'll need to submit, then add the screenshots.

[Credelius]

It's more than tricky, it's beyond any comprehension, but thank you for guiding me anyway 😀

[Sylocheed]

Apologies to OP on hijacking the thread a little bit, but I am also facing some difficulties in terms of app approval and app feedback. I'm not sure what the cause is, and the 10 day approval turnaround makes the feedback loop a little bit punishing (I know you are all working hard!). I tried to create my own thread, but the automoderator flagged it as spam and I can't seem to resolve that either.

@JonFitbit 

I'm struggling to address some feedback I received today on my app submission to Fitbit. For context, it is a simple app that only uses the watch geolocation API and some basic calculation code to determine the sunrise and sunset times for your location (the app doesn't make or need an external Internet API call). The feedback I received in my app rejection is:

#2 App doesn't take GPS location on Ionic & Versa Lite so it doesn't show Sunrise/Sunset time

---

I'm a little bit stuck here: when I use the app on the Ionic and Versa Lite emulators, the code works (and I can change the geolocation in the emulator and see the times change). Also I have a Versa watch and it works on that, which is the most perplexing part to me. I could understand if the Ionic worked and the others didn't as it is the one watch with actual GPS hardware on board, but from what I know, the Versa should work the same as the Versa Lite with respect to geolocation. 

So it is unclear to me why the Ionic and Versa Lite wouldn't work even though the Versa does. And as far as I can see, nothing in Fitbit's sample geolocation code (which I use) appears to be device-specific.

I tried soliciting help from the unofficial Discord but it seemed to be a novel issue. Any thoughts? Thanks!