PWA testing: "Your app is restricted to one or more organizations" - google-play

I've created a PWA of one of our sites to test internally in the company.
I used pwabuilder and created the app inside google play console.
I've tried internal testing, closed testing, as well as open testing but only 2 of our employees are able to see the app in the store and install it. The remainng people who tested get a 'something went wrong' page after accepting the opt-in and clicking on 'download from the play store'
After further investigation, I noticed this little warning:
This is the only thing I can think of that is restricting some users from testing. The 2 employees who were able to install it are using company phones and the others are using personal phones.
How do I change this to not be restricted to my organization? I never selected a 'organization only app' at any point. I can't seem to change this to be open to the entire public.
Any help is appreciated

Related

Google Docs/Slides add-on: other users need to request access when installing from marketplace

Summary: when other users find my Google Slides add-on in the Google Workspace Marketplace and try to install it, they hit a screen saying they need to request access. When they click the button to request access, it sends me (the script owner) a request to share the script file, which should not be necessary. How do I fix this?
I have a Google Slides add-on which has been publicly listed in the marketplace for years (predating the rebranding to Google Workspace). I last updated it in 2019, and recently I wanted to publish another update.
Since this is an old project, I had to go through migrating the add-on to its own standard GCP project and then getting OAuth verification for the (not very sensitive) scopes it needed. This is all done now. All throughout, the add-on has continued being listed in the Google Workspace Marketplace, even though no new users could use it.
All that is done, but other users are still unable to install the add-on from the Marketplace. Now, when they try to do so, they'll get a small new window pop up saying they need to request access - seemingly to the script file of the add-on. This shouldn't be necessary. Does anybody know why it's happening?
If you want to try yourself, the add-on is called Superuser Tools, and the Marketplace listing is here.

Can’t change developer website in Google Play Store

Dose anyone know how the edit/remove my developer website in the new google play console? the ‎new console doesn’t have a website field in the account details anymore, there is no way to change ‎the URL I provided when I first created my developer ‎account, the new Google Play console only ‎allows me to change the website of the developer page.‎
I need to change my developer website that I provided when I first created my developer ‎account ‎‎“trackaty.com” because it’s currently owned by someone else who is redirect it to a gambling website ‎which prevents me from updating any of my apps.‎
I tried to find out who registered my old domain, and I find out the new owner registered it from a ‎Chinese company called Xin Net Technology, I thing they are famous for supporting spammers. ‎
I even thought about transferring all my apps to a new developer account, but the documentation ‎states that the original account and all the apps need to comply with all policy guidelines before ‎transferring anything, which solves nothing.‎
It worth to mention that few of my old removed apps by me used to link to trackaty.com, but the ‎email I get says the problem is in the developer website, I guess that means it’s the account website ‎itself not any of my old removed apps.‎
So, dose anyone faced a similar problem or know how you change the developer website?‎
I had a similar problem when trying to add developer website for adding app-ads.txt file. It seems that they changed its place in new Google Play Console. And developer page menu is confusing developers. Adding my website to developer page didn't work.
So here it is in new Play Console : When you choose a specific app in Google Play Console, click Store Settings on the left panel. You'll see Store Listing Contact Details and there you'll find a box for website.
The developer website can be modified from the Play Console. Go to menu Settings > Developer account > Developer page then you'll see an optional field Website address.
When you update this field, it may take a few days to be reflected in the Play Store.

Play Store updates/installs app using a different account than the one the user made IAP through

On this bug report on Github https://github.com/googlesamples/android-play-billing/issues/2#issuecomment-305380836 we were asked to raise the issue here.
The issue is simple. The user has 2 or more accounts on their phone, let's say xyz#gmail.com and abc#gmail.com. They install an app with the account xyz#gmail.com. They purchase some IAP items. The app updates and now the app is under abc#gmail.com and the user has lost the purchase. This happens a lot when using staged rollouts.
The main issue, as developers we aren't allowed to let the user choose which account to buy with or which account to check for purchases with.
The second issue, the Play Store app on Android ignores the user account selected on the hamburger menu. The only workaround for this is to use the Play Store website as described in this workaround https://github.com/googlesamples/android-play-billing/issues/2#issuecomment-259108286 on the same bug report.
I don't know what the ideal solution is, all I know is that this is a huge hassle for developers leading to a lot of 1-star reviews after each update.
EDIT: As pointed out in a comment, when I refer to multiple accounts I am talking about multiple Google accounts for a single Android User, I am not talking about multiple Android users within the same phone.

Google Apps Marketplace SDK : setup a contextual gadget

Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....

Google Marketplace App Install Flow

When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems?
Some of the documentation says:
We strongly recommend that the administrator be directed through a short, linear series of actions and returned to Google quickly so additional users can start using the application.
I tried testing this out, but it seems like there's some lag between installing and the app showing up in the "more" drop down for Google (I tried installing another app and did end up on the final page but the app still didn't show up in another account. It's been a few hours and it still isn't there) so it's hard to tell if it's just slow or not actually installed on other users' accounts.
Sorry the last section was misleading. This is not a question about the link not showing up immediately.
The new experience for Google Apps Marketplace lets you land the user in the app instead of the admin console. There's now a popup for the app to request permissions and to agree to terms and then the user ends up in the app. One-step installation. Good work Google.

Resources