My app is live on the App Store and there are no crashes on the front end however when I log in to Firebase I cannot find it on the dashboard. I tried copy & pasting the database URL but I got the message saying that there was an error making the request and that I should try again later. Has anyone else encountered this issue and could advise me on who to contact to resolve it?
According to the Firebase Status Dashboard, there should be no issues with the Realtime Database at the moment.
Assuming that your app was associated with your Firebase account previously and just suddenly disappeared, I have not heard of/ encountered anything similar in the past.
One thing to try is to make sure you are logged into the correct account and have selected the correct project.
Since accessing the database directly through its URL says to try again later, this might be a temporary problem that is resolved shortly.
However to make sure, your best option at this point is probably to reach out to Firebase support directly using this form (requires sign-in).
Related
Whenever i try to navigate to App-Specific Shared Secret within ItunesConnect the dialog box attempts to load briefly then I get directed to a crash page titled
"We can't process your request".
I've reset safari clearing all website data and also used other computers.
I've contacted Apple who are sending an email shortly requesting more information but wondered if anyone else had come across a similar fault?
Another very easy solution which worked for me:
Use safari
SOLVED
The problem was due to not previously having created a master shared secret.
Once I did this then I could generate the shared secret for the specific application.
I has a similar issue, when I was getting invited to join Apple Developer Program. I tried joining through the invitation link and I would always get the "We can't process your request" message.
The solution was to:
Log in to an iPhone/iPad with that particular Apple id.
Try to install an app.
You will get a terms and condition pop up that you should accept.
Install the app
Wait for a while until Apple fast servers update your status (around 1 hour for me)
Now you should be able to proceed without the weird message.
I think need to update Mac OS to latest will solve problem. Alternatively you can use google chrome browser.
I am using firebase realtime database in my iOS application.
I am using insert into database and find user depending on filter query in my application.
It all works fine.
Sometimes suddenly my ipad and iPhone stop responding to firebase queries.
Many a times it happens that same application runs perfect on one device and doesn't work on other .
Or same build when deleted and installed stops working on ipad/iphone.
To troubleshoot this I generaly recreate my firebase authentication client id and replace my GoogleServiceInfo.plist.
But this is not the solution as sometimes it works and sometimes not.
Can anybody help regarding this issue?
I had similar problems, it seems that there is a bug for GET request from the database. What I have done is send a Post request i.e.
var rootReference = FIRDatabase.database().reference()
referenceToPath.setValue(values)
Where values are any dictionary of say type [String:String], this writes to the database and it seems to unlock the database and you can read form it.
I have an iOS App on the App Store, and it connects to Google Drive. In the past week or so, I've noticed two new problems in my live app.
The App suddenly stopped logging in. I would get a 401 - invalid_client. I found a lot of questions/answers for this problem, but they were all for people who couldn't get it working. Mine was working for about two years and then stopped working a couple of days ago. After trying a lot of things, I found that I was using <id>#developer.gserviceaccount.com as my Client ID, and when I changed it to <id>.apps.googleusercontent.com it worked again. I don't know why this change fixed it, and even knowing that this fixes it, I can't find if this is the correct/appropriate solution.
I explain my second problem, which is very specific here, but skip to the next paragraph to get to the point. The second issue is a a result of Google changing the way their API calls respond, and this is why this wasn't an issue when we submitted the latest version of the App to the App Store. Google has changed the way the explicitlyTrashed property of their GTLDriveFile class. Per their spec, this property should be either an NSNumber containing Yes, or null. They have recently changed it so that it is always an NSNumber set to either Yes or No. This is what's breaking our functionality.
Anyway, these are two changes Google has made on their end recently that currently has my customers on hold since I have to fix this and push it out. My question is if there's a place to keep up with these changes that Google is making recently. Also, if someone knows or can point me to why the first issue is happening, I would greatly appreciate it.
For the first issue, the reason why it got resolved by using [id].apps.googleusercontext.com is because it it requesting an authorization token from an app to the server, as opposed to a Server to Server transaction using impersonation ([id]#developer.gserviceaccount.com). This is the right solution for both android and IOS apps requesting a token.
As for your second question, the best way to keep up to date with the latest changes is through their official blog: http://googleappsdeveloper.blogspot.com/
Another resource is the G+ Google Drive Developer community: https://plus.google.com/communities/107264319205603895037
I'm using the Parse iOS SDK and sporadically getting the NSInternalInconsistencyException 'User cannot be saved unless they have been authenticated via logIn or signUp'. I've read a lot about this error, and it seems to come up when apps try to save a ref to another user on the iOS side (instead of Cloud Code) or when apps try to modify an unautheticated user. I am attempting to do neither of these -- I'm able to trigger it when trying to save a string property of the logged in user. As I mentioned, this error occurs sporadically, so it's very difficult to track down, but I wanted to see if anyone had any suggestions.
When I change my [currentUser saveInTheBackground] calls to the synchronous [currentUser save] I do not seem to see this error. And to reiterate, it only occurs after signing out with one user and signing in with another, but does not occur with any type of consistency. If the crash the app and reopen, I'm able to save for that user.
I've found a similar threads around the web referencing a similar issue:
Parse SDK on iOS: 'NSInternalInconsistencyException', reason: 'User cannot be saved unless they have been authenticated via logIn or signUp'
https://groups.google.com/forum/#!topic/parse-developers/UZ1ywdpUFVQ
I'm using the iOS SDK 1.6.5 (this error also popped up on 1.6.3) and have parse localDataStore enabled.
Any help/suggestions would be greatly appreciated! Also, not sure if this is the right place to post -- please let me know if not. I tried the Parse Google Group a few days ago, but have not received any responses and am don't know if it's a bug, so decided the FB bugs site was not a good place to post.
I am trying to get Open Graph share actions to work on iOS. It's working some what, if I request the open graph url using the Open Graph Debugger first everything works as expected. However if I don't do this the preview in the share dialog is displayed for a seconds or so and then fades out. The post button is also disabled.
What I am seeing in the backend is that if I use the Open Graph Debugger or paste the object url into my own status I am getting requests from a Facebook server (69.171.234.117). However when I share directly from the application I am seeing a request from another Facebook server (173.252.74.115) this server doesn't seem to be able to read the Open Graph data correctly.
Has anyone seen anything like this before or know what's causing it?
EDIT: I've filed a bug with Facebook for this issue. Will updated here if it changes.
EDIT2: Facebook has confirmed this bug and is working on it. The suggested workaround for now is to trigger an initial scrape by using https://graph.facebook.com/?id={url}&scrape=true when the object is created.
EDIT3: Facebook closed the bug report and claimed the issue is solved in there latest SDK. I will verify this and report back.
EDIT4: This seems to be resolved now from my testing.
I encountered this issue before, it turns out that instances of custom open graph objects that are hosted on your server are instantiated only when they are related to for the first time.
Only when the first edge in the FB graph is assigned to your object is it that it obtains an Identifier and it exists in FB's records.
This first edge can only be created using the FB app or the open graph application.
After that's done you will be able to get a unique identifier for your object
GET https://graph.facebook.com/?ids=YOUR_OBJECT_URL
Then you could perform the share using the returned ID
Also see this SO post which supports my claim.