iam4x/pokemongo-webspoof

Command /usr/bin/codesign failed with exit code 1

Open

#361 opened on Aug 7, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (2,141 stars) (279 forks)batch import
help wantedquestion

Description

I open the pokemon webspoof app up and connect my phone as normal except I get an error saying "Command /usr/bin/codesign failed with exit code 1" it says the issue is in this folder "/Users/yourname/Library/Developer/Xcode/DerivedData/pokemon-webspoof-ekrbzdsynghbnhaowlrqmlfxubkk/Build/Products/Debug-iphoneos/Pokemon WebSpoof.app: errSecInternalComponent" I go to that folder and try to open the file but it says "You can’t open the application “Pokemon WebSpoof” because PowerPC applications are no longer supported." I even restarted my mac, deleted pokemon go webspoof files and reinstalled them and I still get the same issue. Note: all I did was close pokemon go webspoof and re open it and when running the app it said that message.

Contributor guide

Tech stack
javascriptreact nativeios
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Xcode installediOS development certificate
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the code signing error by checking Xcode's code signing settings for the target. The error mentions PowerPC applications no longer supported, which may indicate a mismatch in architecture or deployment target. Consider deleting derived data and validating certificates in Keychain. Look at the repository's README for setup instructions and check if any existing PRs address this issue.