Skip to content
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

[BUG] Issues related to heroku deployment #115

Closed
2 tasks
apexweeb opened this issue Jul 10, 2021 · 18 comments
Closed
2 tasks

[BUG] Issues related to heroku deployment #115

apexweeb opened this issue Jul 10, 2021 · 18 comments
Labels
bug Something isn't working released

Comments

@apexweeb
Copy link

I'm submitting a ...

  • [.] bug report
  • anything else => Please do not submit support requests here. Open a discussion instead and ping me.

I'm running

  • [.] the latest version
  • anything else => Please update to the latest version and retry.

What is the expected behavior?
A clear and concise explanation of the expected behavior.

What is the current behavior?
A clear and concise explanation of the current behavior.

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)
Other info if you wish.

Cant deploy to heroku
Says "We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy."

@apexweeb apexweeb added the bug Something isn't working label Jul 10, 2021
@apexweeb apexweeb changed the title [BUG] [BUG] Issues related to heroku Jul 10, 2021
@ItzBoiz
Copy link

ItzBoiz commented Jul 11, 2021

yes this is very annoying these salesforce bois aren't letting us to live happily.
The second option is to use on replit. BUT you can only deploy the sniper to replit IF U can make private repls.

@apexweeb
Copy link
Author

apexweeb commented Jul 11, 2021

yes this is very annoying these salesforce bois aren't letting us to live happily.
The second option is to use on replit. BUT you can only deploy the sniper to replit IF U can make private repls.

Well isnt there any solution to use it in heroku beacuse the other snipers have issue called "payment source required to redeem gift"

@apexweeb apexweeb changed the title [BUG] Issues related to heroku [BUG] Issues related to heroku deployment Jul 12, 2021
@nichevulcan20
Copy link

yes this is very annoying these salesforce bois aren't letting us to live happily.
The second option is to use on replit. BUT you can only deploy the sniper to replit IF U can make private repls.

Well isnt there any solution to use it in heroku beacuse the other snipers have issue called "payment source required to redeem gift"

Python Nitro snipers aren't banned on heroku its a good news but the developers of those snipers are inactie. also for payment methods we can use nasmo ccgen website and for checker nasmo checker and for address we can use fakeaddressgenerator

GiorgioBrux added a commit that referenced this issue Jul 14, 2021
@GiorgioBrux
Copy link
Owner

I'm aware of this issue and I'm trying to find a workaround.

@nichevulcan20
Copy link

Bois just be patient. Not only this sniper is having this issue, but even other snipers which are also coded in js are having the same issue. the thing is salesforce probaly updated its tos and the snipers now violate the tos. Till then don't try other snipers on main account cuz they can be dangerous and may disable our accounts. The most trusted snipers are just from GiorgioBrux and eternal.

@GiorgioBrux
Copy link
Owner

Update: The repo has been apparently manually blacklisted, fork and then update the heroku URL to point to your repo and it will work. Instructions in readme soonTM.

@nichevulcan20
Copy link

Update: The repo has been apparently manually blacklisted, fork and then update the heroku URL to point to your repo and it will work. Instructions in readme soonTM.

EPIC TY BRO

@apexweeb
Copy link
Author

Update: The repo has been apparently manually blacklisted, fork and then update the heroku URL to point to your repo and it will work. Instructions in readme soonTM.

TY

@GiorgioBrux GiorgioBrux pinned this issue Jul 14, 2021
@ghost
Copy link

ghost commented Jul 21, 2021

for update ur fork use Pull

@notquitethereyet
Copy link

still doesnt work even after forking and using this repo :(
image

@GiorgioBrux
Copy link
Owner

@quiet69 I can't find the fork on your profile. Did you delete it?

@notquitethereyet
Copy link

@GiorgioBrux yes I deleted it :( I'll try again and send you a screenshot again tomorrow

@notquitethereyet
Copy link

image
@GiorgioBrux

@GiorgioBrux
Copy link
Owner

@quiet69 Sorry for the delay, I thought I had answered. Your fork is also apparently blacklisted, the only thing you can do is use another github account. Maybe an org will also work, not sure.

@notquitethereyet
Copy link

@GiorgioBrux i just downloaded your repo and added it to a new repo in my github and it worked

@notquitethereyet
Copy link

@GiorgioBrux getting error on heroku
-----> Building on the Heroku-20 stack
-----> Determining which buildpack to use for this app
-----> Node.js app detected

-----> Creating runtime environment

   NPM_CONFIG_LOGLEVEL=error
   NODE_VERBOSE=false
   NODE_ENV=production
   NODE_MODULES_CACHE=true

-----> Installing binaries
engines.node (package.json): 14.x
engines.npm (package.json): 7.x

   Resolving node version 14.x...
   Downloading and installing node 14.17.5...
   Bootstrapping npm 7.x (replacing 6.14.14)...
   npm 7.x installed

-----> Installing dependencies
Installing node modules
npm ERR! code EINTEGRITY
npm ERR! sha512-wBvR+6PacWS4QVg8+mdx6oJ8mgLpyoqRHApwxFwMByQ/9Yg02ieNBJ5zbqpzxjFJCanEtL1J4gQk91DRVS2Aag== integrity checksum failed when using sha512: wanted sha512-wBvR+6PacWS4QVg8+mdx6oJ8mgLpyoqRHApwxFwMByQ/9Yg02ieNBJ5zbqpzxjFJCanEtL1J4gQk91DRVS2Aag== but got sha512-rpVCvcO69UauZb1cruiTLzFCsWmRsn7pz8TRO2E1K2yHCRMx8kFD9UifMuQHC01T7Ot3cMmaVXE6etlLL/4q0Q==. (26256 bytes)

   npm ERR! A complete log of this run can be found in:
   npm ERR!     /tmp/npmcache.z0b3V/_logs/2021-08-25T12_04_54_327Z-debug.log

-----> Build failed

   We're sorry this build is failing! You can troubleshoot common issues here:
   https://devcenter.heroku.com/articles/troubleshooting-node-deploys
   
   If you're stuck, please submit a ticket so we can help:
   https://help.heroku.com/
   
   Love,
   Heroku

! Push rejected, failed to compile Node.js app.
! Push failed

image

@GiorgioBrux
Copy link
Owner

@quiet69 My fault, will fix asap.

@notquitethereyet
Copy link

build still failing :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

No branches or pull requests

5 participants