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

Could not launch "Pokemon WebSpoof" #465

Open
ghost opened this issue Mar 14, 2019 · 21 comments
Open

Could not launch "Pokemon WebSpoof" #465

ghost opened this issue Mar 14, 2019 · 21 comments

Comments

@ghost
Copy link

ghost commented Mar 14, 2019

My phone has denied the launch request. It worked this morning and now this comes up and its the same on any device I try. Anyone else with that problem recently?

@k-webdesign
Copy link

Ha! Got the same error and researched a bit online but found no real solution. You were faster with opening a ticket :)
Screenshot 2019-03-14 22 13 50

@SDB-H
Copy link

SDB-H commented Mar 15, 2019

Same thing here, related to an update of the iOS (12.1.4)?

@ghost
Copy link
Author

ghost commented Mar 15, 2019

Same thing here, related to an update of the iOS (12.1.4)?

Same results with an older iPad that doesn't have that update

@Pritski
Copy link

Pritski commented Mar 15, 2019

Yep same problem here

@megusta63
Copy link

Same Problem here!

@trisapple
Copy link

It's related to how Apple signs the certificate and creates the Provisioning Profile to "sign" the app. It has been broken since yesterday or 2 days ago. I guess the only way now is to just wait for Apple to do the relevant fixes.

Screenshot 2019-03-15 at 9 26 55 PM 2

Also, I did a bit of research and found that under the "Entitlements", "get-task-allow" must be "true" for the debugger to attach to the app on your device, and also to modify the GPS on your iOS Device.

Of course you can Edit Scheme and uncheck Debug Executable, but this would not allow you to use the debug feature to tweak the GPS.

@trisapple
Copy link

trisapple commented Mar 15, 2019

Same thing here, related to an update of the iOS (12.1.4)?

It's definitely not related to iOS 12.1.4. It just came out of nowhere a day or 2 days ago. It seems to be a widespread issue affecting everyone that uses Xcode. Besides, every app I attempt to install on my own device using Xcode generates this error.

@ghost
Copy link
Author

ghost commented Mar 15, 2019

Also, I did a bit of research and found that under the "Entitlements", "get-task-allow" must be "true" for the debugger to attach to the app on your device, and also to modify the GPS on your iOS Device.

Of course you can Edit Scheme and uncheck Debug Executable, but this would not allow you to use the debug feature to tweak the GPS.

Where do I find that file?

@trisapple
Copy link

Where do I find that file?

~Library/MobileDevice/Provisioning Profiles

@patzsy
Copy link

patzsy commented Mar 16, 2019

It's related to how Apple signs the certificate and creates the Provisioning Profile to "sign" the app. It has been broken since yesterday or 2 days ago. I guess the only way now is to just wait for Apple to do the relevant fixes.

Screenshot 2019-03-15 at 9 26 55 PM 2

Also, I did a bit of research and found that under the "Entitlements", "get-task-allow" must be "true" for the debugger to attach to the app on your device, and also to modify the GPS on your iOS Device.

Of course you can Edit Scheme and uncheck Debug Executable, but this would not allow you to use the debug feature to tweak the GPS.

Is there a way to edit the mobileprovision file i.e. set the get-task-allow to be true? Seems like the only way I can find to do it is to enroll Apple Developer Program which has the editing feature.

@0ddj0b7
Copy link

0ddj0b7 commented Mar 16, 2019

glad im not the only one ive been trying everything and nothing has worked

@trisapple
Copy link

Is there a way to edit the mobileprovision file i.e. set the get-task-allow to be true? Seems like the only way I can find to do it is to enroll Apple Developer Program which has the editing feature.

I tried editing it with TextEdit but it renders the file unusable (no preview in Quick Look)

@molonlabe88
Copy link

This is ridiculous. I can't believe apple screwed up this bad and has still not fixed it.

@trisapple
Copy link

Hopefully this gets fixed soon...

@crazystone2407
Copy link

After now more than a week, starting with the failing provisioning profiles, Automatic signing works for me again. The downloaded/automatically generated and downloaded provisioning profiles allow the signing. However, the launch is denied, when I want to Debug the executable (which is a must in this case). Without debugging everthing runs well (just not taking the position...). Also I can "Ask on launch" in the Scheme, however, then the position is as well not taken. The program is finished immediately, once started manually on the phone.

Mayby soembody is fit enough to work a workaround on the basis of the "Ask on launch" option, potentially modifying the code, that it does not finish immediately.

All very frustrating...

@molonlabe88
Copy link

https://www.reddit.com/r/jailbreak/comments/b0tjce/discussion_error_42_what_is_it_and_how_you_can/

here is a way to get around it i guess.

@0ddj0b7
Copy link

0ddj0b7 commented Mar 19, 2019

Cool thanks I took a look through that thread and it seems like it should be a work around but i havnt tried it. If anyone does could you let me know? I'm actually in awe that such a system wide failure hasn't been addressed yet unless this was intentional on apples part to gain more paid developer subscription.

@victeo88
Copy link

victeo88 commented Mar 19, 2019

I follow these steps and it is fixed!

UPDATE (3/19/2019): Great news! It seems like Apple fixed the issue, now the .mobileprovision file has the 'get-task-allow' property set to true which means the debugger should work normally as before. Just do the following:

  1. Uncheck the Automatically manage signing option in the General tab of target settings
  2. Fully close Xcode
  3. Delete .mobileprovision files under ~/Library/MobileDevice/Provisioning Profiles/
  4. Delete the following certificates in Keychain Access:
    • iPhone Developer: [email protected] (xxxxxxxxx)
    • Developer ID Certification Authority
    • Apple Worldwide Developer Relations Certification Authority
  5. Remove Webspoof from your iOS devices
  6. Reboot your Mac and iOS devices
  7. Launch webspoof
  8. Change the Bundle Identifier to anything else (you might change it back after it works)
  9. Plug in your devices, click on Run, trust your certificate on your iOS devices
  10. It should work now

@trisapple
Copy link

I just removed the certificates in Keychain Access and it worked

@crazystone2407
Copy link

Thanks @victeo88 your description worked perfectly for me now as well. I had two/three frustration moments (Xcode telling me with an ever before unseen error message "Device locked"even if it was not) but after that, things worked again perfectly.

@0ddj0b7
Copy link

0ddj0b7 commented Mar 21, 2019

Thanks a lot @victeo88. up and running!!

Appreciate it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

11 participants