I’m stuck with my Google Drive app. I tried to get it into the Google Apps Marketplace but it got rejected. The issue is about the authorization domain. They want me to use a different URL format for the request.
Here’s what they said:
Your request starts with one URL but it should look more like another URL with DOMAIN_GOES_HERE in it.
I’m confused about what this means. I used the Java DrEdit example as a base for our Drive operations.
Can anyone tell me if it’s possible to use this new domain format with the Google API Java Client Library? If so how do I do it?
Also I’m worried about file permissions. If I change the domain will I still be able to do all the Drive operations I need?
I’ve tried to contact Google but haven’t heard back. Any help would be great!
I encountered a similar issue when submitting my Drive app to the Marketplace. The authorization domain change is indeed necessary for approval. To implement this with the Google API Java Client Library, you’ll need to modify your authorization flow configuration. Specifically, look for the setRedirectUri method when building your GoogleAuthorizationCodeFlow.
Regarding file permissions, rest assured that changing the authorization domain won’t affect your Drive operations. Your app’s ability to access and manipulate files should remain intact, provided you’re using the correct scopes.
One often overlooked aspect is ensuring your Google Cloud Console project settings align with your code changes. Double-check that the authorized redirect URIs in your project settings match the new format.
If you’re still facing issues, consider posting your specific code snippets on Stack Overflow for more targeted assistance. The community there is quite helpful with Google API-related queries.
hey, i’ve been thru this. the new url format is easy to switch up in the java client, so just update your auth settings. file perms won’t change. check your cloud console if issues persist. good luck!
I’ve been through a similar situation with my Drive app, and I can relate to your frustration. The authorization domain issue can be tricky, but it’s solvable.
From my experience, you’ll need to modify your app’s configuration to use the new URL format. It’s definitely possible with the Google API Java Client Library. You’ll want to look into the ‘setAuthorizationServerEncodedUrl’ method when setting up your authorization flow.
As for file permissions, changing the domain shouldn’t affect your Drive operations. I’ve made similar changes before, and all my file access remained intact. Just make sure you’re using the correct scopes when requesting authorization.
One tip: double-check your Google Cloud Console settings. Sometimes, the issue lies there rather than in the code itself. If you’re still stuck, the Google Developers forum can be more responsive than direct support.
Keep at it – once you get past this hurdle, the Marketplace submission process gets much smoother!