I have GoogleApps Marketplace app in which I'm using "Integrate with Google" button to start the google OAuth2 process. The button disappeared two-ish days ago as far as I can tell. I'm receiving the error 404 - https://apis.google.com/marketplace/button
Is there a temporary issue in google API? I can update my app if needed as well. I've also made a ticket in Google's issue tracker https://issuetracker.google.com/issues/113072052 (inadvertently marked as a feature).
Exact same symptoms as: "Integrate with Google" button suddenly disappeared (receiving 404)
this should be fixed now. Sorry for the inconvenience.
This affected only listings that are unlisted in Chrome Web Store. Installing unlisted apps is not supported in G Suite Marketplace and we would like to understand how/why you are using this feature.
Related
I am struggling to login on Xamarin Forms with Facebook on android specifically, ios is. still working, the implementation in my app is as described in this article: https://evgenyzborovsky.com/2018/03/09/using-native-facebook-login-button-in-xamarin-forms/ and has worked perfectly until Facebooks changes. Now when users try to login we get the following error message on android only: "Login disabled", "For your account security, logging in to Facebook from an embedded browser is disabled. You may be able to continue by updating the app you're logging in from and trying again."
I have read the write up on Facebook Developers here: https://developers.facebook.com/docs/facebook-login/android/deprecating-webviews
But the solution does not seem to be clear for Xamarin Forms as we are using Xamarin.Facebook.Android version 7.1.0
Any help or being pointed in the right direction will be appreciated.
The package has been updated few days ago to the version 11.2.0.1.
https://www.nuget.org/packages/Xamarin.Facebook.Android/11.2.0.1
I had the exact same issue and it's now fixed.
So the situation is as follows, I used 3 different packages from pub.dev all for the purpose of user authentication with Twitter (3-legged Oauth). My main package which I was using in my app was flutter_twitter_login. This worked flawlessly until today when I run my app everything was still working (launched the sign in page and signed in successfully) until the authorisation function was triggered when then I was redirected to the 'Sorry, that page doesn't exist' page with a search bar on Twitter (error code 34). I thought maybe this is a problem with my package like a new bad update, simply not the case, all 3 most known packages for user authentication failed in the exact same way. The other 2 I tested were twitter_login and flutter_twitter.
Keep in mind that 2 days ago I had a successful login within my app with a confirmation message and valid HTTP message returned. Most of my code were examples given by the flutter package creators.
I made no changes to my code, yet it broke seemingly on its own
After seeing some relevant problems over the years reported on stack overflow and the Twitter developer forums I suspect that the problem may be with the API endpoints (which my flutter packages manipulate, not me). Any opinions/directions?
PS: I have seen issues that say about the app becoming deactivated, disabling 3-legged Oauth by accident and account getting blocked all 3 of these are not the issue I checked/tested thoroughly.
Relevant Twitter forums post: https://twittercommunity.com/t/flutter-twitter-login-stopped-working-with-authentication-error-sorry-that-page-doesnt-exist-code-34/152435
It seems that the issue was on the API side and it has been resolved without me changing anything to my code. The issue lasted 48 hours.
I created a DialogFlow app that works perfectly in my developer account.
But I need to test it as another user, so in my Google Action simulator, I added another test account as a OWNER to the project.
I verified this user has OWNER status in both the DialogFlow and Google Action UI.
They are able to edit both projects with full access.
However, when the test account tries to use the simulator it says:
Sorry, this action is not available for your app. Sorry, this action
is not available for your app. In the simulator, you are only able to
invoke actions that you have added to your app. For more information
on how to invoke your app, click here
https://developers.google.com/actions/discovery/explicit
This makes no sense to me:
I verified the test user has OWNER/ADMIN status on both DialogFlow and Google Actions for the project.
In DialogFlow, I verified the Google Assist is pointing to Default Welcome Intent as the default intent.
In Google Actions, I verified that the Default Welcome Intent is visible on the BUILD > ACTIONS UI.
As others suggested, I tried renaming the app several times with no luck.
I tried publishing an Alpha version, with still no luck.
My gut tells me it is some sort of permission/visibility problem, but I am completely stuck. Any ideas would be of great help.
EDIT:
THIS ISSUE HAS BEEN SOLVED. SEE COMMENT BELOW.
"I revisited my activity controls and noticed my "Web and App Activity" had a special clause due to organization permissions. I completely missed it due to the confusing UI. Posted a picture in the main thread. Thanks for reminding me to double check that area."
After you asked your company admin to enable this feature, it should be same as the image in below.
This error message is quite misleading. I have encountered this error a couple of times, and generally the problem was with one of the privacy settings in my Google account.
In this case you should go to https://myaccount.google.com/activitycontrols, confirm that you are logged in using your test account, and make sure the following are enabled:
Web & App Activity
Device Information
Voice & Audio Activity
Its been three weeks my app (GSuite spreadsheet add-on) is in "Pending Review" state after unpublishing it through chrome web store developer dashboard.
I also don't know why it is visible in marketplace as well when I already requested Google for unpublishing this item.
Query: Its already three weeks gone, any idea how much max time Google takes to unpublish an GSuite marketplace app from Chrome web store developer dashboard?
Here is a related SO post about the unpublished apps in web store.
See this full answer from the post:
if app is unpublished then is will not be available for download, will
not appear in in-store search results, and simply cannot be installed
from store. No details information from Google Play can be received
even with direct URL to the application. Unpublishing however does not
affect existing installations (so apps will not be automatically
removed from any device that got it installed already). Also existing
users still would be able to update if they are on older version.
And you cannot have another application with the same package name, no
matter what.
EDIT
Please note that you unpublish (and this means just what name says,
nothing more) not just APK - you hide all related stuff (app's page in
Google Play etc). To end user it looks like the app is gone. For you -
it is still in your console, you can edit description, images, see
comments, stats or update APKs etc., but unless you publish it again,
nobody will see these changes.
I integrated Facebook SSO in my Windows Phone 8 app yesterday and it was working properly. I tested it several times and on multiple devices and all was working. I submitted the code to my repository and today when I ran the code on the device the SSO wasn't working properly.
It starts off by starting the Facebook App as usual but then it shows me the dialog that it usually shows in the browser (with the typical message asking if I don't wish to install the Facebook application on my phone, which is installed) and even if I sign on it doesn't go back to my app.
I have not changed a single line of code since yesterday so I really have no idea of what must be happening. I checked if the Facebook App had been updated but it wasn't.
Does anyone have any idea of what might be happening?
It was an issue with the Facebook app which they seem to have resolved by today. Now everything is working properly again.