I'm currently finding myself unable to enable the Admin UI. It was enabled before and now does not seem to work.
When I looked at my backends I see this.
Image of Amplify backend environment with a button to enable admin UI.
I then clicked the switch to turn on the Admin UI as shown below.
Image of the Admin UI enable screen.
I clicked it and it says it's enabling in a popup here, before saying it succeeded in another popup here.
I thought this was originally something wrong with my project but it's happening on my other amplify project - is the Amplify Admin UI down for some reason?
P.S. I was going to post this on server fault as this post says but there was no tag for Amplify on here.
Sorry this is not an answer, I cannot make comment so I have to write here.
I wasted a whole day by meeting the exactly the same issue.
At the same time, I tried to run Amplify pull --appid --envName several times, it always stuck there.
Amazon status page shows everything is fine now but I cannot believe it.
I also posted a question here but it seems nobody answered it.
I hope this issue was discovered by more people and Amazon finally can fix it, I believe it's not a problem on our side.
The issue was resolved as shown in this ticket I opened.
https://github.com/aws-amplify/amplify-adminui/issues/206
Have you tried selecting the environment and then clicking Open Admin UI?
I also wasnt able to login clicking in the URL and with my credentials, but clicking there worked.
Related
We have an app in Expo that is logging in to Firebase with Google, but for some reason after going through the dialog it offers to select an app, which is shown twice, instead of selecting it automatically.
What is the proper configuration for solving this issue? I've had a look at this and that, but we cannot remove schema as it wouldn't work without it. There's a bug report on this issue, so I'm hoping someone managed to work around it here.
Tried connecting to https://brandonchen1.github.io/ after github said your site is ready to be published. Tried opening website in different browsers and the repository is https://github.com/BrandonChen1/BrandonChen1.github.io.
Can anyone help me figure out why the webpage is still displaying a 404?
Stumbled upon this question when my pages weren't getting published. Posting what I did in case someone else runs into this too.
Check GH's status as suggested by this community question and make sure everything is green.
Then check your repo's Actions tab. Under Workflows, look for pages-build-deployment or something similar and check for any errors in the runs. The Actions page can be found at https://github.com/<username>/<repo name>/actions.
i have read all the answers ( i could find on the matter), and they say, if you are a developer, tester or admin of the application, you should be able to test the app without any problem. I have tried as a admin of the app, developer, tester etc (all the roles given in the developer dashboard) no luck, next i have tried with the test users, still no luck, when i ask the user for the permission (publish_stream), the popup always says
Submit for Login Review Some of the permissions below have not been
approved for use by Facebook.
I have setup the "privacy policy link", i have uploaded the application icon, entered the application description, still no luck. in the mean time, the other two permissions i ask (user_photos and email) work with no problem.
I can't get what i am doing wrong. has anyone had problems like this?how did he manage to solve them? any help will be much appreciated.
P.S the only thing i haven't tried is to submit the freaking app for review, but the app is far from done, so i think, the review will be rejected
You really don´t need to go through the review process for testing, unapproved permissions work for every Admin, Developer or Tester of the App. publish_stream is deprecated though, what you probably want is publish_actions.
If it still does not work with an Admin/Dev/Tester and the publish_actions permission, i´d suspect a bug. In that case you could report it: https://developers.facebook.com/bugs/
I am working on an app currently in sandbox mode and I need to test out the posting of user's scores... When I try the following I get the above subject matter. The odd thing about this is that I have the been granting the said permission (using my personal user account).
// var PERMS = 'user_likes,friends_likes,publish_stream,user_photos,photo_upload,publish_actions,offline_access';
https://www.facebook.com/dialog/oauth?scope='+PERMS+'&client_id='+APP_ID+'&redirect_uri='
I don't see the permissions in the Auth Dialog(I'm using the Enhanced Auth Dialog. They said its hidden :-S) but I am not "denying" any permissions and process the Auth Dialog successfully....
Can anyone tell me whats up here?
Have you submitted a bug? If not you should, and I will vote on it as well. It is definitely a new bug. I can show my repro on it.
I just got this today as well. Within the last hour. Googled it, and found this post. Last week I successfully moved 5 apps to use timeline open graph, and the enhanced auth dialog. Today, moving a new app, I made sure to add publish_actions, added it to the code, uninstalled the app, and reinstalled it with the new dialog, and tried to run a timeline post. Got the same error. I don't get this error on the apps I moved last week, they work just fine (just tested). I also noticed a couple of other changes to the UI when editing in the dashboard. The preview windows are gone on the auth dialog page. You can still fill in the aggregations in the open graph section. My guess is they made some changes last week, and broke something with new app permission changes.
I'm using the xfbml Add To Timeline social plugin (https://developers.facebook.com/docs/reference/plugins/add-to-timeline/), but when I click it the permissions dialog I get just says "Access my basic information" and sure enough it isn't actually getting me the publish_actions permission I need to use the timeline. I tried specifying the perm explicitly on the tag like so:<fb:add-to-timeline show-face="false" mode="button" perms="publish_actions"></fb:add-to-timeline> but no luck.
This was working fine yesterday and suddenly now it isn't. I'm wondering if this has something to do with my adding and removing my app from my facebook account multiple times?
This was driving me crazy for a long while. In my case, I fixed it by enabling 'Enhanced Auth Dialog' under the Advanced tab of my app settings.
When asking for publish_actions Facebook shows a preview screen of what sort of aggregations your app will create on their timeline.
In other words, if the preview isn't working, Facebook won't ask for the permission so you're asking in vain. Facebook doesn't make this clear in the docs, but everything needs to be perfectly setup with your app on Facebook to get this to work right.
Enable Enhanced Auth Dialong in the advanced settings of the app
Make sure you have at least one action and one object set up in the open graph section
For each action you must have an aggregation set up.
If you do not do all of these steps, there can be no preview and so Facebook won't ask for permission no matter what.
I faced the same issue. I fixed it by doing the below mentioned two thiings.
a. Enabled 'Enhanced Auth dialog' from 'advanced' setting of the app.
b. blanked 'user and friend permissions' along with 'extended permissions' tab on 'auth dialog' page.
I am not sure what it did, but it started working.
BUT.. Even though the authentication works and the posts are reflecting on my timeline, the add-to-timeline button still shows, 'Add to Timeline'..
The other trick i used is to keep checking the app permissions under account setting tab of my profile page.
Hope this helps !
From Apps -> Settings -> Auth Dialog:
While in Open Graph Beta, the 'publish_actions' permission can only be
requested from developers and test users of your app. The
'publish_actions' permission will be ignored if requested from any
other user.
I had the Enhanced Auth Dialog enabled in the Advanced Settings, yet this did not work until I added a Aggregation Preview for the activity. Strange, but true.
Hope this helps.
The publish_actions permission appears only if the user has added timeline OR if your app is a game. I suppose it will also be available for apps when Timeline will be rolled out to all users...