-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy Heroku #123
Comments
I got the same issue.... any updates? |
I never experienced this issue. Can you post some screenshots? |
try to see what npm pkg is causing this issue
…On Wed, Jan 12, 2022 at 10:09 AM Mauricio Lahitte ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/18168535/149177451-ca59bb49-b99d-4aff-94b3-5cd64eb42c16.png>
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGRD5NYZV56AR7BDIPPPGTUVWRUBANCNFSM5KUPAQBQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
@ghostnetrn @mauriil do you still face this issue? |
Yes Item could not be created: |
Sounds like something you'd need to take care of, @bitcoinvsalts? |
Hi, I also face this issue. Is there any way around this? |
As bitcoinvsalts.com is EOL, the heroku deployment won't be fixed anymore. The repo is kept as is and is to be understood as archived. |
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.
The text was updated successfully, but these errors were encountered: