Amplify-js: iPhone has denied the launch request. Internal launch error: process launch failed: failed to get the task for process 7661

[Luckygirlllll]

Describe the bug
I was making settings for AWS Pinpoint IOS, when I'm trying to run the app on my real device, I got an error: "iPhone has denied the launch request.
Internal launch error: process launch failed: failed to get the task for process 7661'

To Reproduce
Steps to reproduce the behavior:

1. Follow official guide for setting up Push Notification AWS Pinpoint,
2. Uncheck automatically manage signing
3. Import provisioning profile

Expected behavior
App runs on the phone

Desktop (please complete the following information):

• OS: IOS

Smartphone (please complete the following information):

• Device: Iphone
• OS: IOS

Additional context
When I was using "Automatically manage signing" I was able to install an app on the phone, however, I was not able to receive any push notification from AWS Pinpoint in that case, I'm not sure whether or not "manual signing" is required or not.

[Luckygirlllll]

This problem was solved by going in Xcode to Product -> Scheme -> Edit Scheme -> change Executable to Ask on Launch

[haverchuck]

@Luckygirlllll It sounds like this issue was solved, so I am closing the ticket.

[feudadrien]

This problem was solved for me by going in Xcode to Runner -> Signing & Capabilities -> Signing (Debug) -> Check "Automatically Manage Signing" +Add Team

[RicardoBarroso]

For me the problem was solved following the @Luckygirlllll suggestion but selecting an option with a different description (probably it was updated on the meanwhile):

Product -> Scheme -> Edit Scheme -> Wait for executable to be launched

[TunvirRahman]

For me it was signing issue. I was trying to build in device with production provisioning profile.

[RicardoBarroso]

Despite my last answer which did work for a previous app now I've seen that on a new one the solution was to check Automatically Manage Signing.

Be aware that if your build scheme is using Debug or Release the corresponding signing provisioning profile on Build Settings also must be set to Automatic.

[RicardoBarroso]

I stumbled again on this issue and now I was able to solve it despite NOT using Automatically Manage Signing.

You only need to go to Product -> Scheme -> Edit Scheme and uncheck Debug executable on your build scheme: