Disallowed useragent как исправить

Some Android and iOS users are reportedly seeing the Error: disallowed_useragent whenever they try to open, log in o or sign in to certain apps that they’ve legitimately downloaded from the App Store or Play Store. This error typically appears when the end-user tries to uses some kind of Google authentication.

Why is the Error: disallowed_useragent occurring?

This error will come up if you are trying to use an application that fails to make a valid login request to Google.

In the vast majority of cases, the Error: disallowed_useragent will occur because the Android or iOS app makes a login request that Google rejects. The most common reason for this rejection is an unauthorized browser agent (the app is using a deprecated browser agent that Google no longer accepts).

How to Fix the diasllowed_useragent error?

Unfortunately for those hoping for a cure-all fix, this is very likely to be a problem beyond your control. Most likely, this is a problem that the app developer will need to address.

Fortunately, there are some mitigation steps that you should try if you’re stuck with the disallowed_useragent error:

Now that you are aware of the mitigation strategies available to you if you find yourself in this particular scenario, let’s go over each of them in detail.

1. Update the app to the latest version available

Before giving up and concluding that the issue is beyond your control, start by assuming that the developer already adapted the app to meet the latest Google guidelines.

So before contacting the developer, start this troubleshooting guide by ensuring that the app that triggers the Error: disallowed_useragent is updated to the latest version available.

Of course, the instructions on doing this will be different depending on if you’re using Android or iOS, but we’ll guide you through both scenarios.

Just jump to the sub guide (below) that’s applicable to your mobile operating system:

1.1. Update the problematic app on Android

Android will auto-update your apps, but the timeline on which these actions will be deployed depends on either you’re on mobile data or Wi-Fi or if you have the habit of keeping your phone in battery-saving mode or not.

If there’s an update pending for the problematic app that’s showing the disallowed_useragent error, you can manually install the update by visiting the Manage Apps & device menu.

For step by step instructions on how to do this, use the guide below:

Note: The instructions below will be identical regardless if you’re using a smartphone or tablet Android device.

1. From the home screen of your Android screen, open up the Google Play Store app.
2. Once you’re inside the Play Store app, tap on your profile icon (top-right corner).
3. From the context menu that just appeared, tap on Manage Apps & Device.
4. Once you’re inside the dedicated Manage apps & device menu, tap on the Manage tab, then select the Updates available filter and find the app that is giving you issues.
5. If the problematic app has a pending update waiting to be installed, hit the Update button and wait for the operation to complete.
6. Once the installation of the update is complete, open the application again and see if the issue is now fixed.

1.2. Update the problematic app on iOS

Apple is a lot more strict than Android when it comes to ‘encouraging’ you to update your apps with the latest available updates. But ultimately it’s up to you if you want to have auto-updating enabled or not.

If app auto-updating is disabled on your iOS device and the problematic app that’s triggering the disallowed_useragent error has a pending update, follow the instructions below to install it:

Note: The instructions below are identical and will work for the iPhone, the iPad, and the iPod.

1. From the home screen of your iOS device, tap on the App Store icon.
2. Next, tap on your Apple profile icon at the top of the screen to bring up the App Store settings menu.
3. Inside the context menu that just opened, go ahead and scroll down to the Available Updates section.
4. Once you’re there, click on the Update button associated with the app that’ triggering the error.
5. After the update is successfully installed, open the application again and see if the problem is now fixed.

2. Contact the App Developer

If updating the application did not help in your case, it’s very likely that you’re stuck with the Error: disallowed_useragent prompt due to the fact that the OAuth authorization request to Google is classified as an embedded user-agent that’s currently deprecated.

Since it’s clear that the application you are trying to use makes a login request that is no longer accepted by Google, the solution is clear – the app needs to be updated as per Google’s requirements or move the app to an alternative authentication method (such as GTMAppAUth).

However, none of these resolutions will be at your fingertips if you’re a regular user. All you can do is let the app developer known of this issue utilizing the official channels.

If you’re encountering this error with an app developed by a small indie team, it’s likely that your only option of contacting them is via the official developer email available inside the store listing.

Follow one of the sub guides below (depending on the mobile platform you’re facing the issue on) for instructions on discovering the contact info of the app developer:

2.1 Contact the developer on Android

If you’re experiencing the Error: disallowed_useragent issue on the Android ecosystem (phone, tablet or smart TV), you can easily find the contact information for the app developer inside the store listing. Just keep in mind that some of these devs are very slow in responding to user concerns, so don’t hold your breath.

Follow the instructions below to get in contact with the Android app developer:

Note: You can follow the instructions below on smartphones, tablets, or Android TVs. The instructions are almost identical – the differences are outlined in the NOTE paragraph.

1. Open the Google Play Store on the affected Android device from the home screen shortcut.
2. Next, use the search function inside the Google Play Store to find the app that you’re having issues with.
3. Once you manage to find the appropriate store listing, tap on it.
4. Inside the dedicated store listing, scroll down to the Developer contact section and expand the associated drop-down menu.

   Note: If you do these steps from an Android TV, you’ll find the Developer contact information under Full Description.

5. Inside the Developer Contact menu, you should see all the available options for contacting the developer.
6. The final step would be to explain the issue in detail to make the developer aware of the issue so they can fix it.

2.2 Contact the developer on iOS

If you’re experiencing the issue on an Apple device running on iOS or watch OS, you can get in touch with the developer via the App Support button inside the app product page.

The good news is, iOS developers, need to comply with Apple’s strict guidelines, so expect to get a response fairly quickly.

Here’s how to get in contact with an iOS developer and ask them to fix the disallowed_useragent error:

Note: The instructions below can be followed on the iPhone, the iPad, and the iPod touch. You won’t be able to view the developer contact info on watchOS. In case you’re experiencing the issue on WatchOS, you will need to follow the instructions below from the iPhone that’s paired with the Apple Watch.

1. Start by opening the App Store on your iPhone, iPad, or iPod Touch. The easiest way to do this is from the home screen.
2. Once you’re inside the app store, use the search function at the top to find the app that’s giving you issues, then tap on it from the list of results.
   Note: If, for any reason, you can’t find the listing, tap on your account button or your photo (top of the screen), then tap on Purchased, then tap on the app.
3. When you see the app’s product page, scroll down to the Ratings & Reviews section, then tap on App Support.

   Note: If you don’t see the App Support section, it’s because you aren’t signed in with the correct Apple ID.

4. Inside the App Support section, you should see a list of all the available contact options.
5. Pick one contact option and explain the issue as thoroughly as possible so the developer will know when is the problem encountered by the end-user and how to fix it.

Here is the unfortunate answer: Yes, you are using the example from Google’s iOS Quickstart, the “native SDK” as you call it. That’s outdated, however, as it uses exactly the embedded web view that Google doesn’t want you to use anymore.

If it did work before, but has stopped doing so all of a sudden (like I experienced myself), it may have to do with you changing something related to the client ID. For client IDs that exist for some time, there seems to be a longer grace period until Google hard-blocks the web view use (there should still be just some warning for now, I understand). A new client ID I created recently for unrelated reasons, seems to have caused just that, getting me stuck in having to replace Google Drive authentication code for a new release at short notice.

As to the options (that the so far only other respondent to your question lists from the Google blog post), after a bit of research GTMAppAuth seems to be the most viable option to me, as I am not interested in complete user sign-in and -out. But I may be wrong there.

GTMAppAuth has sample code for iOS, yet just in Objective-C. I have yet to make it through that. In general, your code logic will change like so: Your current solution does authentication purely within your app. It’s asynchronous, but doesn’t leave your app. The new solution requires you to initiate authentication within your app while preparing and remembering your callback functionality. The authentication initiation then opens a browser outside, which, once done causes a URL callback in your app delegate. In your app delegate, you then check for your prepared callback and, depending on the result status of the outside call, notify the user about success or failure of the outside authentication.