"Prepare for verification" complains about scopes?

[zenobase]

Started migrating my app from the Fitbit API to the new Google Health API, but got stuck at the "Prepare for verification" step. Specifically, I see this message:

> The following scopes are not available for external usage, please remove them from your app: https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly

That doesn't sound right: Surely I can retrieve activity summaries, like with the old API?

All the requested scopes (incl e.g. googlehealth.sleep.readonly) also have a "this scope is not yet verified" warning, not sure if that is a blocking issue too?

[DorisFitbit]

Hi @zenobase 

Thanks for reaching out. We are currently working to reproduce the behavior and will get back to you as soon as we can. 

[zenobase]

Thank you; let me know if you need any additional information for reproducing this behavior!

[DorisFitbit]

Hi @zenobase 

Just a quick update - I've shared this issue with the Engineering team. I will provide more updates once I hear any. Thank you. 

[zenobase]

I removed the offending scope (though it's not clear why I shouldn't be able to access activity data). This unblocks the form to submit the application for verification, but when I submit that form (after checking all the boxes), I get "Your app could not be submitted for verification: The attempted action failed, please try again"...

[tipako]

I am facing the same problem. Would be great if it could get resolved soon 

[Anasboyka]

Same here and its the only scope i need and i cant use it in my app because of this issue

[DorisFitbit]

Hi all, 

I’ve escalated the priority of this issue internally to ensure it gets the necessary visibility. I’ll follow up with you here as soon as I have a status update. Thank you for your patience. 

[deferdie]

Hi Doris,

Just checking if there are any updates on this or if there is a ticket we can track progress?

Thanks,

Ferdie

[DorisFitbit]

Hi @deferdie 

The Engineering team is currently working on the fix. We're hoping to get this resolved by the end of the week. If not, the timeline will shift to after upcoming Google I/O event (May19-20).

[matdefer]

Is this timeline confirmed? we need to get some reliable information to prioritize work.

[DorisFitbit]

Hi all, 

The Engineering team has confirmed that the issue is now resolved. Could you please try again and let us know if you encounter any further trouble?

[tipako]

Yes, unfortunately, I can still not submit for verification. I get this error in the Google Cloud Console:

[DorisFitbit]

Hi @tipako 

Sure, let me check with the team.