I am trying to generate a REST api ID, api Key pair. I have generated the api id, but when I go to generate the api key I get the error "Something went wrong, please try again". I waited a few minutes and then tried again- no change.
Any advice?
We tried to test this on the portal and it is working fine ,Could you please try to logout from the portal and retry
Related
I cannot pass user info to firebase database, and I think this is the issue. My Authentication part works well, and can pass image to firebase storage. Can anyone explain to me what does this error mean?
Here is my method:
Also, in logcat, it shows "one way function results will be dropped but finished with status OK and parcel size 4", which I think is the same issue if I am not wrong
Here are my dependencies:
Can anyone help me please?
Searching elsewhere I found this answer:
"Seems like you have enabled App Check in your Firebase project. This feature was announced a few days ago, so it's unlikely you will find any info online. Check the docs to see if you have followed all the setup steps: https://firebase.google.com/docs/app-check "
I'm getting this error after I try to add a new app and click 'Register App':
"There was an unknown error while processing the request. Try again."
I've looked at these and they have the same problem but didn't have solutions that worked:
Can't create Firebase project - There was an unknown error while processing the request. Try again
GCM - Getting Error message "There was an unknown error while processing the request. Try again." when creating new project
Firebase: There was an unknown error while processing the request. Try again.
I'm not using multiple Google accounts. I've tried signing out and in again, tried changing the package name, and the Firebase status page doesn't show any outages.
I had the same problem, After a long research fond that it was been OAuth 2.0 Client Id limit. In order to resolve, I have deleted all OAuth 2.0 Client IDs from Google cloud console, then try again. It works fine for me.
Steps to remove OAuth 2.0 Client IDs :
Open 'https://console.cloud.google.com/'
Select your project from the top navbar
Select APIs & Services from Left Side panel
Select Credentials in the left panel
Go to OAuth 2.0 Client IDs
Select all unused Entries (!Carefully)
Click on delete on the top bar
Done, go to firebase console try again
It may solve your problem!!
Have you tried changing your package name? I'd same issue,that was resolved by changing package name. As Firebase saves deleted package names as well.
You might reached number of OAuth 2.0 client IDs limits. There is a limit of around 30 client IDs that can be created within a single project.
Make sure you sign out all your google accounts and sign in with the account for your specific project. I'm normally signed in to 3 or 4 accounts and ran into this error issue. Did as I mentioned and it worked.
The operation has failed (Reason: [object ProgressEvent])
I am getting the above-mentioned error while creating a new project. This got resolved by logging out and logging in again
I was using Bing Custom Search API for the past week with no problems thanks to the free trial, but today, I tried upgrading to the S1 plan, since the API was sending error messages. I tried regenerating the key as well, but despite doing both of these things, I was still getting errors and unable to use the API.
However, I was able to make calls using: https://www.customsearch.ai/applications, where I was able to use my API key to test endpoints and get the results I expected. What baffles me is that my nodejs code which hasn't been modified aside from the subscription key should still work with the upgraded plan, but it doesn't.
I should be able to help here. Let us do little bit of troubleshooting once:
First go to https://www.customsearch.ai/applications -> click on your instance name ->Click on "Production" tab on top -> Try making API call on this page by providing Query and Subscription key you got. If this works, go to the next step.
On the page mentioned above you would have seen Custom Configuration ID and Subscription Key. Make sure those two are same in your node.js code. Ideally this should work.
If it still doesn't work, please share your error code so that I can get better understanding of the error you are getting.
I am using the authentication API as directed here: http://docs.microsofttranslator.com/oauth-token.html
Everything was working fine for about a week and suddenly today at around 11:55pm eastern time, all calls to get a new token give 500 errors with the following stack:
http://pastebin.com/uQ3VL6Am
We simply make a POST request to https://api.cognitive.microsoft.com/sts/v1.0/issueToken
with header 'Ocp-Apim-Subscription-Key' set to our key
I tried using our second API key, and it still does not work. I tried regenerating another key, and it still does not work. Our account manager says that the account should be in good standing.
Thank you
This issue has been resolved by Microsoft as of 6pm PST 1/30/17.
Facing a very strange issue.
Following this guide https://azure.microsoft.com/en-in/documentation/articles/app-service-mobile-xamarin-forms-blob-storage/ to implement File Sync in Xamarin Forms app.
The Get method in my service (GetUser, default get method in App service controller) is being called thrice & on the 3rd iteration it gives me a 404 resource not found error. First 2 iterations work fine.
This is the client call
await userTable.PullAsync(
null,
userTable.Where(x => x.Email == userEmail), false, new System.Threading.CancellationToken(), null);
If I remove the following line,
// Initialize file sync
this.client.InitializeFileSyncContext(new TodoItemFileSyncHandler(this), store);
then the code works just fine, without any errors.
I will need some time doing a sample project, meanwhile if anyone can shed some light, it will be of help.
Thanks
This won't be an answer, because there isn't enough information to go on. When you get a 404, it's because the backend returned a 404. The ideal situation is:
Turn on Diagnostic Logging in the Azure Portal for your backend
Use Fiddler to monitor the requests
When the request causes a 404, look at what is actually happening
If you are using an ASP.NET backend (and I'm assuming you are because all the File tutorials use ASP.NET), then you can set a breakpoint on the appropriate method in the backend and follow it through. You will need to deploy a debug version of your code.
this is sorted now, eventually I had to give it what it was asking for. I had to create a storage controller for User too, although I don't need one as I don't need to save any files in storage against the users.
I am testing the app further now to see if this sorts my problem completely or I need a storage controller for every entity I use in my app.
In which case it will be really odd as I don't intend to use the storage for all my entities.