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.
Related
I have been trying to generate an iOS certificate from the Codename One Control Center, launched from Intellij. Every time I submit my apple iOS developer credentials, and then input the 2 factor authentication code, it returns with this error:
REST request failed due to internal CLI failure. See server error log.c5307525-1805-4360-d4ca9d46cad0
I enrolled in the Apple Developer Program, and I believe I've agreed to all of the Apple Developer agreements and such, and I have exactly one device registered, as well as that one device set as the trusted device, so it receives the 2 factor authentication notifications. I'm also not sure where I am expected to be able to see the "Server error log" as I have searched around for that.
I've only been able to find 2 other cases that seem similar to mine but neither give me a clear idea of what the problem is or how to fix it. They do however seem to resolve their problems. I really don't have any more ideas as to what the problem could be.
Codename One IOS signing
Unable to Login to iOS Account from CodeNameOne
Another odd thing about this problem is that usually I get this error after being prompted to input the 2-factor authentication code, but sometimes I'm never prompted to input the code before getting the error, yet I will still receive the 2-factor authentication code text message on my phone despite there being nowhere to use it.
Any help is appreciated.
I have made some updates to the certificate wizard to try to work around this issue. Please give it another try. If you run into another problem, please post the error message again, and I'll look it up in the logs.
Ok so after looking around a bit further, I was finally able to find a git issue post that seemed similar to mine, and at the very end of the thread (linked below), someone mentioned that you need to be signed into that apple id on the device, not just have it as a trusted device. My iOS phone was showing up in the account because I was logged into the Apple Developer App, but this is not enough. Thanks for helping.
https://github.com/codenameone/CodenameOne/issues/2779
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
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,
I have no idea how to troubleshoot this problem to findout what is going wrong.
When my deployed app is required to send an email it loads for a while then gives a 500 error. It sends the email fine in development and if I run the app in production on my local machine it also sends the emails fine so I cant reproduce it on my local machine and look at the logs. If I just deployed an update or fix then it will send the emails fine in the deployed version sometimes, but for the few times it works it stops working shortly after.
I'm using google cloud platform to host the app but can find a way to see what is causing the emails to not be sent and give me the 500 error. the GCP logs are useless and just say there was a 500 error at x time with no indication in what caused it.
How can I troubleshoot this problem or maybe what could be causing this?
Somehow narrowed it down to be a firewall problem from my google cloud instance. By default they block port 465 (the port I was using to send emails).
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).