I just migration my App data from Parse to Back4App and followed the steps to set up back4App configuration. But now when I hit the Parse API with reference to back4App. It is continuously giving me following error: [Error]: The certificate for this server is invalid. You might be connecting to a server that is pretending to be “files.parsetfss.com” which could put your confidential information at risk. (Code: 100, Version: 1.14.2) Error]: Network connection failed. Making attempt 1 after sleeping for 1.171176 seconds. Can anyone please provide a solution for this kind of error. I have updated Parse SDK in my App as well as ParseFacebook SDK.
Thanks in advance.
Ratneshwar
The issue is related to PFFile object in parse, There is some issue in migrating parse to any other server.
I am also facing the issue and i have reported a bug on git forum of parse.
Here is the link:
https://github.com/ParsePlatform/parse-server/issues/2781
May be you should try by reporting your issue here.
Hope this helps!
Related
When I tried to submit an App to Itunes Connect I got the following error.
App Store Connect Operation Error
An error occurred while trying to call the requested method validateAssets. (1272)
Any suggestions on what I need to change to be able to submit my app?
Looks like theres an apple developer outage: https://developer.apple.com/system-status/
Try multiple times, I've managed to upload build right now in less then 100 attempts xD
I recently got an app from an iOS developer, and it is working with his bundle identifier in xCode. but when I change the bundle identifier to mine, it stops working(database is not connecting). What should I do to make it work? Making a new Firebase account and use my bundle identifier to get a new GoogleService-Info.plist and replace it with his GoogleService-Info.plist is enough ? (I did that too but still not connecting to the database) what have I missed ?
UPDATE
I want to connect to my new empty database that comes with the new firebase account , not the previous database.
If you read the GoogleService-Info.plist the DATABASE_URL should be different in two files. Thats why you can't connect to the previous database. You can export data from the first one and then import those json to the new database. Is this solution okay for your case?
Updated
Okay, step by step. There are error messages showing in the XCode console. Do you know how to find them? I created a Firebase file, replaced a new plist. And then I run the app, when I try to sign up. It shows a pop up "Problem with creating a new user, Problem connecting to database, Pleaes try again later". But the important thing is! This is not the error code. When you look at the XCode console, it shows:
<FIRInstanceID/WARNING> Failed to fetch default token Error Domain=com.firebase.iid Code=501 "(null)" UserInfo={msg=Missing device credentials. Retry later.}
<FIRInstanceID/WARNING> Failed to retrieve the default GCM token after 5 retries
Then you can google it.
How to fix Failed to fetch default token error?
after trying so much time I found the error it was
FIRAuthErrorCodeOperationNotAllowed = 17006
Indicates that email and password accounts are not enabled. Enable them in the Auth section of the Firebase console
to get rid of this all I have to do was go to,
https://console.firebase.google.com/project/myproject/authentication/providers
and select Sign-In method and enable email and password
I have implemented the requestPasswordResetForEmailInBackground code to my app (xcode 7 using swift) for a login-screen. I used several tutorials, but I'm having the following error:
"Internal server error."} (Code: 1, Version: 1.12.0).
I'm wondering if more people have seen this problem, because the site of Parse states that this is a problem we can't solve.
Thanks.
This feature is not available on Parse Server. The team is working on implementing it but has not given a timeframe (yet) on a release. I you have an app in production and really want to get a mail service out now, check out services, like Mailgun. I expect that, when the Parse team adds the mail service, it will be a lot better than what was offered on the "old Parse."
All of a sudden, we are getting an error authenticating with Nest and Firebase. The error code is 9999, and the message is "blocked". The source code has not changed on the app side, so it seems like something has changed on the server side.
I see a similar issue here, however they are getting a message of "too many requests", instead of "blocked".
Can anyone help us resolve this issue? Thanks.
This error occurs when you have too many concurrent open connections to Nest using the same access token. This is a different issue to "too many requests" issue which, as indicated, is to protect the battery in the thermostat.
It seems that you may be opening up Firebase or REST streaming connections and not closing them properly before opening up a new connection. Once a Firebase connection is open you should use this connection for reading and writing any new data and open a new connection only if when this connection is severed.
Could you please post sample code on how you are handling opening, closing and using the connections? Your sample code will help analyze the specifics of the issue.
I have been using my app during the day with no issues but I am now getting the following error on all requests I make to Parse to get objects:
2014-09-03 20:24:21.913 App[3407:332f] Error: Failed to initialize mongo connection (Code: 159, Version: 1.2.20)
Has anyone else experienced this and if so know the reason behind the message.
Thanks in advance.
EDIT:
Parse is down once again (no surprise) Here is the link to the new bug if you are having the same problem of mongo DB going down. The twitter and status website should be the same. Hopefully they fix this sooner rather than later.......
https://developers.facebook.com/bugs/665440236886829/
I am having the same problem and posted on the developers website you can follow it here.
https://developers.facebook.com/bugs/300758356778621/
Edit: They are experience a lot of different problems it sounds like right now. Facebook was down for awhile but is now up. They are still working on parse errors and crashes according to what the developer left on the link above.
So it is coming up slowly but people are still experiencing errors on top of following the bug at the link above here is there twitter account.
https://twitter.com/ParseStatus
Also their status website.
http://status.parse.com/incidents/m9k6y5qbz2dk
Should be up shortly (hopefully).