Iphone Unit Testing error : permission denied with google toolBox - iphone

I followed many tutorial to set up a unit testing project for Iphone but i always get the same "permission denied" error when i build the project.
Here is what i do :
Get the latest source for Iphone Unit Testing
Follow the instruction to set up the unit testing framework (Create a new project, add a new target, copy the necessary toolbox files into my project, add the script to my target, etc)
Build the project (Emulator closed)
I expected :
Executed 0 tests, with 0 failures (0 unexpected) in 0.001 (0.001) seconds
But i have the following error :
/vdaTest/Calculation/build/Calculation.build/Debug-iphonesimulator/unitTest.build/Script-7BDF2E1A10172C2000279979.sh: line 2: /vdaTest/googleToolBox/RuniPhoneUnitTest.sh: Permission denied
I'm using this version of the toolBox:
Revision 158: /trunk
On :
Mac OS X version 10.5.7
I'm using Xcode 3.1.3 with Iphone simulator 3.0
I've search here and on google for that error but i didn't find anything... Any help would be greatly appreciated !
Thanks,
Vincent.

Big thanks to the xcode-users mailing list! This solution works on my mac:
chmod +x RunIPhoneUnitTest.sh
This might do the trick. "Permission denied" is the error you get when you try to tun a shell script that is not executable.

Related

Error Module 'flutter_secure_storage' not found when try Product ->Build for -> Profiling

well this error occurs to me when I try to make my app in production.
The app is created with flutter and I was able to create the apk for android, but when I try to do it for ios it won't let me.
The file that I am opening is Runner.xcworkspace and the problem is the import of a flutter library, it seems to me that I have to make some kind of connection with the pods.
here is the error, I want to tell you that I do not want to run the app, but to make an installer
The error that occurs when building a release (ie. flutter build ipa) and not when running a debug build is:
/[REDACTED]/ios/Runner/GeneratedPluginRegistrant.m:48:9: fatal error: module
'flutter_secure_storage' not found
#import flutter_secure_storage;
~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
1 error generated.
note: Using new build system
For me regenerating Podfile in the following way solved the issue:
rm ios/Podfile && flutter build ios
See Closed [ios][release] GeneratedPluginRegistrant.m Module not found
#43986

Encountered an error communicating with IBAgent-iOS. Failed to boot device iPhone Xs

I am getting an Error on the top of my interface builder in Xcode 10.3 and while clicking on report bug and checking the log.txt file I found out that fails to open simulator. However I am not starting any simulator.
Here is the Error found in Log.txt
Encountered an error communicating with IBAgent-iOS. (Failure reason: IBAgent-iOS failed to launch): Failed to boot device iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown) for context <IBCocoaTouchToolLaunchContext: 0x7fe80e754ad0> toolName = IBAgent-iOS, description = <IBCocoaTouchPlatformToolDescription: 0x7fe80e2a0290> System content for IBCocoaTouchFramework-ElevenAndLater <IBSimulatorDeviceTypeDescription: 0x7fe80fab2f90> deviceType=com.apple.CoreSimulator.SimDeviceType.iPhone-XS (Failure reason: Failed to boot iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown)): Unable to boot the Simulator. (Failure reason: launchd failed to respond.)
Error Domain=com.apple.InterfaceBuilder Code=-1 "Encountered an error communicating with IBAgent-iOS." UserInfo={NSLocalizedFailureReason=IBAgent-iOS failed to launch, NSUnderlyingError=0x7fe80ae44440 {Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out" UserInfo={NSLocalizedFailureReason=Failed to boot iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown), NSLocalizedDescription=Failed to boot device iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown) for context <IBCocoaTouchToolLaunchContext: 0x7fe80e754ad0> toolName = IBAgent-iOS, description = <IBCocoaTouchPlatformToolDescription: 0x7fe80e2a0290> System content for IBCocoaTouchFramework-ElevenAndLater <IBSimulatorDeviceTypeDescription: 0x7fe80fab2f90> deviceType=com.apple.CoreSimulator.SimDeviceType.iPhone-XS, NSUnderlyingError=0x7fe80bd300f0 {Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out" UserInfo={NSLocalizedFailureReason=launchd failed to respond., NSLocalizedDescription=Unable to boot the Simulator.}}}}, NSLocalizedRecoverySuggestion=Please check Console.app for crash reports for "IBAgent-iOS" for further information., NSLocalizedDescription=Encountered an error communicating with IBAgent-iOS.}
If anyone still looking for an answer to this after Xcode 13 update, I have tried everything they mentioned on the internet and nothing worked except one. The only thing that worked is the complete re-installation of Xcode. Completely uninstall/delete Xcode first and restart the mac and reinstall Xcode then all should be good.
Delete Xcode from Applications Folder and Empty Trash.
Go to ~/Library/Developer and Delete CoreSimulator, Xcode, XCTestDevices Folder. Empty trash
Goto ~/Library/Caches and delete everything starting with com.apple.dt.Xcode, Empty trash
Then Restart your Mac and reinstall Xcode. I used my downloaded Xcode app, AppStore installation will also work, I guess.
Now it all working.
Before that, I have changed the storyboard file using Open as Source Code mode (coz I couldn't open it in Interface Builder - Xcode just hang)
I changed the storyboard design device to iPhone 13 instead of the older device version it had.
<device id="retina6_7" orientation="portrait" appearance="light"/>
I change the existing line with this line. It kinda solve another issue of Xcode hanging, when trying to open with Interface Builder, but it didn't solve Encountered an error communicating with IBAgent-iOS issue when trying to install the app. That issue only got solved when I completely reinstalled the Xcode.
I have managed to fix it just by changing preview device on interface builder
In my case it helped:
clean project
remove derived data
close Xcode
restart Mac
I used DevCleaner XC helper app:
https://apps.apple.com/us/app/devcleaner-for-xcode/id1388020431?mt=12
removed everything, and after that restarted mac. No XC reinstall needed.
This problem caused because, I deleted all directories under "Library/Developer/Xcode" for a purpose. But, I realised I also deleted wrong directories in same time. Then I put back directories from the Bin. It is solved for me.
If you have or have had multiple versions of Xcode open, you may need to reboot or completely re-install the CoreSimulatorService, an evil, globally installed background service that somehow remains online and available to many versions of Xcode despite it being compatible with only one version.
See more here: https://stackoverflow.com/a/72946533/731285
Other symptoms of this issue: Simulators not showing up in the Window > Devices and Simulators listing and simctl throwing errors and being unable to find base iOS SDKs similar to the following:
$ xcrun simctl list
...
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-15-5 --
iPhone 8 (55A90310-8202-4A0D-968B-00F440D42210) (Shutdown) (unavailable, runtime profile not found)
See also:
Command CompileAssetCatalog failed with a nonzero exit code
Xcode device Unavailable, runtime profile not found
In my case, I just had to set team in
Project > Targets > Signing & Capabilities > Team > Personal Team

Titanium Appcelerator Running error on iOS 9.2

Device: iPhone 5 (Model A1429)
iOS version: 9.2 (13C75)
Titanium SDK: 4.0.0.GA
When I tried to run/distribute my app, I faced this error messages
[ERROR] : ** BUILD FAILED **
[ERROR] : The following build commands failed:
[ERROR] : Ld build/iVirtue.build/Debug-iphoneos/iVirtue.build/Objects-normal/arm64/iVirtue normal arm64
[ERROR] : (1 failure)
The warning in TiApp Editor > Deployment Targets said
iOS development requires [5.0, 9.0) but you have 9.2
Initially, when I haven't updated my Titanium Studio and my iOS version, the app was running perfectly. Please help.
I didn't clearly explain it before. The app i made was made on Titanium Studio, so installed the Appcelerator Studio and have the app exported. Now, it's working well. Thank you all, now i can close this matter.
Try to update the Titanium SDK to the latest 5.1.2.GA & all other components as well, because as you said that the app was working fine before so it is something related to the updates.
Use Titanium Studio to update everything available.
This seems to be a problem in your run configuration (or tiapp.xml). I suggest you first delete the run configuration, run the app again to define a new run configuration. Also check tiapp.xml to see if you have any references to iOS version?
You should also clean your project prior to running it after having deleted the run configuration :-)
/John

clang: error no such file or directory: */Debug-iphonesimulator/MailCore/MailCore

I am using mailcore2 in my ios app from fetching my gmail account emails on my device. I have changed the ios sdkversion from 6.1 to 6.0 in the mailcore2 scripts bcz I am trying to compile and run the app using iPhone simulator 6.0 which uses ios sdkversion 6.0. Doing so I am getting the following clang error.
clang: error: no such file or directory: '/Users/shujaat/Library/Developer/Xcode/DerivedData/MyTestApp-ditognlaoajwldfliplqecnxqbfj/Build/Products/Debug-iphonesimulator/MailCore/MailCore'
While trying to compile and run my app using iphone simulator 6.1 (uses ios sdk 6.1), with no changes in the ios sdk version in the shell scripts, I am getting the following error:
/bin/sh /Users/shujaat/Documents/WemoTech/Products/WantList/sourcecode/ThirdPartyLib/MailCore2/Externals/builds/workdir/20130930192723/src/libetpan/build-mac/update.sh
configuring
running prepare-cyrus-sasl.sh
prepare sources
patching file lib/client.c
building tools
generated makemd5i386 properly
building for iPhoneOS - armv7
CONFIGURE FAILED
Command /bin/sh failed with exit code 1
These issues are driving me crazy for the last couple of days. Need your help.
Go to your main project target->"Build phases"->"Target dependencies" add mailcore2 ios
You need to read Check Adding MailCore to Your iOS Project carefully.
These issues are fixed now. I want to explain what I did to get rid of them for others facing same issues:
I made a separate project, and made mailcore2 as a part of it (didn't include the #import line in any of the project files at first). I compiled and run the project and copied the resultant mailcore 2 from it to my original project. It's compiling and running fine now.

Appcelerator iPod build problems

I'm using Titanium Studio (1.0.0.201104272233) and Titanium Developer (1.2.2) and have just begun my app development. It builds just fine to the iPhone simulator. Yay! BUT. . . when I attempt to build to the device, I get this error:
[INFO] Performing clean build
[ERROR]
[ERROR] Error: Traceback (most recent call last):
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.0/iphone/builder.py", line 1306, in main
execute_xcode("iphoneos%s" % iphone_version,args,False)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.0/iphone/builder.py", line 1066, in execute_xcode
output = run.run(args,False,False,o)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.7.0/iphone/run.py", line 39, in run
sys.exit(rc)
SystemExit: 65
Here's the full build log: pastie.org
I'm using OSX 10.6.7, Titanium SDK 1.7.0, ios SDK 4.2 (or 4.3). I have xCode3 in /Developer and xCode4 in /xCode4/ and a receding hairline from this issue. I'm trying to build to an iPod touch with software version 4.3.3.
Studio seems to handle the parallel location of xCode4 better than Developer when working on the simulator. I've deleted the build folder a number of times and attempted different ios/Titanium SDKs.
The key to this is that one can use the *.xcodeproject file and go to build the application in xCode. This will give the developer a whole different debugging environment with error messages particular to the iPod/Apple requirements and certifications to get all the settings right. Though they may appear to be correct and accurate in Titanium Studio or Developer, there can still be errors or conflicts. In my case, I had duplicate certificates in my keychain and some errors in my provisioning set up which, as you can see in the log wasn't apparent at all from Titanium Studio or Developer.
Thanks a bunch Brian for your assisting question and guidance.