When I clone my production Zapier app to version 2.0.0, in order to make some changes, I get an error message stating "Internal Server Error".
I'm not receiving any other details on what might be the cause of this error.
Does anyone know what might cause this?
Thanks,
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 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!
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 just finished installing the Devise gem without any problems and now I am trying to install the Sendgrid add-on from the command line using:
heroku addons:add sendgrid:starter
I have done this before with other apps without any problems. However with this time I am getting this error:
Adding sendgrid:starter on languagecheck... failed
! Error Provisioning User - Error creating customer
I have gone through my code several times. I tried logging out and back into Heroku without any problems. I tried searching for someone with a similar error, with no luck.
I cannot find any other error messages elsewhere. Does anyone have an idea for why this is happening? Could it have something to do with Sendgrid's server being down? Thanks in advance for your help!
I contacted Heroku about this issue. They responded with "Sorry for the trouble there. I'm seeing the same error returned for other customers attempting to provision the Sendgrid add-on; looping them in to find out more." I haven't heard back from them yet as to what the reason behind it was, but I'll post it if I ever find out.
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).