Appium studio not responding latest version

Devices \ Emulators Applications
#1

please help i use latest version of appium studio 23_4_9090, im using mac m1

log

Blockquote Number of open channels: 1
2023-06-08 09:19:14.524 DEBUG [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] IOSBridgeManager Notification device connect: 7da47b53fe3a9ef262a73968cae3636d5f0769a6
2023-06-08 09:19:14.532 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager New connected device 7da47b53fe3a9ef262a73968cae3636d5f0769a6 wasn’t found in DeviceManager list
2023-06-08 09:19:16.837 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:20:18.093 DEBUG [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] IOSBridgeManager Notification device connect: 7da47b53fe3a9ef262a73968cae3636d5f0769a6
2023-06-08 09:20:18.093 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager New connected device 7da47b53fe3a9ef262a73968cae3636d5f0769a6 wasn’t found in DeviceManager list
2023-06-08 09:20:23.986 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:21:20.604 DEBUG [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] IOSBridgeManager Notification device connect: 7da47b53fe3a9ef262a73968cae3636d5f0769a6
2023-06-08 09:21:20.605 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager New connected device 7da47b53fe3a9ef262a73968cae3636d5f0769a6 wasn’t found in DeviceManager list
2023-06-08 09:21:25.024 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:21:50.081 DEBUG [pool-3-thread-1] CommunityLicenseUtils Connection status: 200 OK
2023-06-08 09:21:51.163 DEBUG [pool-3-thread-1] CommunityLicenseUtils Connection status: 200 OK
2023-06-08 09:22:22.334 DEBUG [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] IOSBridgeManager Notification device connect: 7da47b53fe3a9ef262a73968cae3636d5f0769a6
2023-06-08 09:22:22.335 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager New connected device 7da47b53fe3a9ef262a73968cae3636d5f0769a6 wasn’t found in DeviceManager list
2023-06-08 09:22:30.360 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:23:15.392 DEBUG [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] IOSBridgeManager Notification device connect: 7da47b53fe3a9ef262a73968cae3636d5f0769a6
2023-06-08 09:23:15.394 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager New connected device 7da47b53fe3a9ef262a73968cae3636d5f0769a6 wasn’t found in DeviceManager list
2023-06-08 09:23:22.731 WARN [7da47b53fe3a9ef262a73968cae3636d5f0769a6 MuxEventListener executor] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:23:30.245 DEBUG [Thread-3] BackgroundTasks BackgroundTasks are shutting down; since now using BackgroundTasks in shutdown hooks is forbidden!
2023-06-08 09:23:30.251 DEBUG [rmv-rsc] JsonWireProtocolAgent Appium shutDownWebServer
2023-06-08 09:23:30.281 WARN [rmv-rsc] DeviceManager Device wasn’t found in DeviceManager list
2023-06-08 09:23:30.287 WARN [KQueueEventLoopGroup-3-1] MuxService Got channel closed notification, Listen to usbmuxd was closed
2023-06-08 09:23:31.537 DEBUG [Exit] CommunityLicenseUtils Connection status: 200 OK

i dont have device for udid 7da47b53fe3a9ef262a73968cae3636d5f0769a6 connect in my mac

and also for the current version i can’t get provisioning profile for my device ios

#2

there seems to be a mass issue with the provisioning profile. i, somehow managed to solve it and am now retracing my steps in an attempt to see what it is.
i have found that it most certainly is not related to the device and maybe not even appium.

#3

Possible solution to the Provisioning Profile issue a possible solution to the provisioning profile issue.