1) When click on the open device in appium studio to launch ios app, i got an error. Even when i am doing manually also, i experienced below same issue.
Error Domain-XCTDaemonErrorDomain Code=13 "Error
kAXErrorInvalidUIelement copying attributes 1102"
UseInfo={NSLocalizedDescription=Error kAXErrorInvalidElement copying
attributes 1102}
Note- I experienced above issue only IOS version- 12.2
2) When i execute IOS automation scripts, Sometimes it shows " Device disable". But, Earlier it works fine.
Please tell a solution for this issue
Please try it on their latest version 12.4. iOS 12.2 works for me in Appium studio v12.4.
Related
Xamarin Forms Project
Microsoft Visual Studio 2019 Version 16.9
Xcode on Mac version 12.4
Using IPad Pro 11 inch running 14.4 as the simulated device and IOS version.
( I tried other simulators )
If I build and run Simulation on the Mac, it works. So i believe it is a remote simulation issue.
If you set IOS simulator to remote it starts and appears to run the simulation
in the simulator but it just shows a black screen.
Ive updated everything I can think of. Mac OS, XCODE on latest available.
Visual Studio, W10, all latest available and everything restarted...
Still it doesnt work. You do see brief at time of deployment dots spinner that reminds of the spinner when shutting down.
How do I fix the back screen simulation. ?
EDIT: With Latest Updates, it works again.
After upgrading to VS2022, upgrading Xcode on the mac.
Even the simulators are now ios15.x
Somewhere is all those updates the problem is gone.
You could have a try with Forget the Device first:
Next step, better need to reboot Mac .
Last, Pair to Mac again with Add Mac manually:
If it also can not work, maybe need to check the quality of network whether is well.
I want to test my apps in the iOS 10 simulator, but I'm not sure where to get the .runtime file for iOS 10. I don't see a download for it under Components in Xcode 8. Where can I download the .runtime file for iOS 10 (if it exists)?
Thanks in advance!
EDIT: I forgot to mention: As I was trying to fix another problem (before I asked this question), I ended up deleting all of my runtimes and redownloading them (except for iOS 10).
I ran into this issue earlier today. After installing Xcode - beta, my simulator was still only displaying iOS simulators 9.3 and below. What eventually ended up working for me was:
Killing the currently running simulator with cmd-Q
Control clicking (right click) on the Xcode - beta icon in my dock
Hovering over "Open Developer Tool"
Selecting Simulator from this menu
Once the simulator launched, I began to see iOS 10 in the Hardware -> Device drop down. Hope that helps.
Xcode > Open Developer Tool > Simulator
close And re-open Xcode again
All ios 10 simulator are already downloaded with xcode8 - beta it self. You can download additional simulators from preference -> Components.
And
You can get data for you app in those simulators at following path.
/Users/User_ACC_Name/Library/Developer/CoreSimulator
Ensure existing simulators are closed. Then open XCode 8 (beta):
Go to menu XCode -> Open Developer Tools -> Simulator.
This worked for me:
Go to App Store and Make Xcode Update 8.0
Open Xcode and it installs the components
Go to Menu "Window" > "Devices"
Add A New Device (Important one that supports iOS 10))
At the end the devices list is updated, and you can run the devices that can run iOS 10 in the simulator
Steps 1 to 5 Screenshots
The iOS 10 Beta Simulator is shipped inside of Xcode 8.0 Beta. You do not need to download anything extra. The primary reason for the large size of the Xcode download is for the three simulator runtimes that it contains.
OK, this has been open for long enough and Xcode 8/iOS 10 are out of beta, plus I solved this problem a week after this was asked, so I'll post my own answer. I ended up redownloading and reinstalling the entire Xcode 8 beta which includes the .runtime file in itself. Bit of an overkill, but I didn't have any other options at the time.
Nothing already mentioned worked for me. I was missing iOS 10.3 simulators in Xcode 8.3.3. What worked for me was to reset the simulators using fastlane snapshot tool:
sudo gem install snapshot
snapshot reset_simulators
Source: https://stackoverflow.com/a/37814682/1318739
I was scouring over stackoverflow and somehow unable to find the answer to my problem. My app builds and compiles just fine, but when i try to run it on the simulator, it throws a __dyld_dyld_fatal_error(). However, when i try to run it on an iOS device, everything is smooth. On a side note, I've have just updated my XCode version to XCode 4.2 to support iOS5
It turns out that I had to reset the settings on my simulator before having to run it without any glitches, and made sure of the correct version of iOS that the application has to run on.
I created an empty Single View application using Xcode 4.2 on OSX Lion 10.7.2 targeting iPhone 5. The project built happily however when launching the simulator I receive the following error message:
iOS Simulator could not find the SDK. The SDK may need to be reinstalled.
I then tried targeting the iPad with the same results. I removed Xcode using the terminal and downloaded a fresh copy from the AppStore. The clean installation generates the exact same error.
It seems that the SDK is not being deployed during installation. Any advice or tips on how I can correctly install the iOS 5 SDK for the simulator to work?
Update
I downloaded the iOS 4.3 simulator which was not installed. The simulator works perfectly if I select the 4.3 SDK but for some reason is not recognizing the folder containing the 5.0 SDK.
Update
I reformatted the MacBook, reloaded a clean OSX Lion without restoring any backups and installed Xcode. Running the simulator directly after the installed worked, however after a reboot and relaunching Xcode the error came back. The SDK itself seems to have been corrupted. Will try and reinstall Xcode again.
After some testing it turns out the problem is caused by a 3rd Party Software. Recently the developer of TotalFinder removed the Asepsis portion of the system and created a separate application for the handling of DS_Store files.
Unfortunately, this breaks the iOS Simulator once installed, and even after uninstalling Asepsis, I needed to rebuild my whole machine to get rid of the error.
Update
BinaryAge is aware of the issue with regards to Xcode 4.2 and it is now listed on the know issues page and a warning banner displayed on the download link.
Final Update
It seems BinaryAge has changed the way Asepsis works and this is no longer an issue with the latest versions.
Did you try "File -> Reset Content and Settings ..." in the simulator ? I also encountered the similar problem, but it worked after I reset the simulator! In fact, I also found it worked after I removed all the existing projects and created new ones, but it occurred again after I restart xcode. Fortunately the "Reset" always works for me and I hope it can be helpful for your case.
I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.