I followed the steps from this website http://iphonedevwiki.net/index.php/Xcode to deploy my app to jailbroken Ipad, but I received error after compile
error: can't exec '/usr/local/bin/ldid3.py' (Operation not permitted)
I set chmod +x to that file but still the same
I tried to execute "ldid3.py" in terminal and there's an error: invalid syntax
I'm using MacOS Lion 10.7.3 with Xcode 4.2.1
Any help will be appreciated. Thanks a lot
I spent a lot of time debugging this problem myself. I don't know any Python, so it took me a while, but the solution is simple. That ldid3.py script never writes the preferences to disk. Simply add f.flush() after the f.write(...). I hope that helps.
Related
I have created fresh project(Hello World) in KMM followed by their official website. In android it works smooth but when I am trying to run in XCode it's giving errors because of which I am unable to build / run the xcode project. I have attached screenshots and logs for my errors. Somehow xcode scheme is not getting generated in the KMM platform that's what I am guessing.
Can anyone please help me understand what am I missing?
Any help would be appriciated.
Following is my dev env:
Xcode 11.4.1
Android 4.1.2
Kotling Plugin version 1.4.30 (stable)
KMM 0.2.0```
XCode Logs:
> Task :shared:compileKotlinIosX64
Downloading native dependencies (LLVM, sysroot etc). This is a one-time action performed only on the first run of the compiler.
Extracting dependency: /Users/fatin/.konan/cache/clang-llvm-apple-8.0.0-darwin-macos.tar.gz into /Users/fatin/.konan/dependencies
e: java.lang.RuntimeException: Cannot extract archive with dependency: /Users/fatin/.konan/cache/clang-llvm-apple-8.0.0-darwin-macos.tar.gz.
> Task :shared:compileKotlinIosX64 FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':shared:compileKotlinIosX64'.
> Compilation finished with errors
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 7s
1 actionable task: 1 executed
Command PhaseScriptExecution failed with a nonzero exit code ```
[![enter image description here][3]][3]
I reached out to community for this and finally found the solution. Here is the link to that issue which I raised and solved this problem.
If anyone else is going through this same issue it mostly cause of corrupted kotlin file.
Also try checking your cmd line tools in XCode as per comments.
Hope this helps someone. Cheers.
If the project doesn't run right away even on opening it from Xcode and shows the shared framework is missing, Then try generating the shared framework for iOS platform using terminal. Navigate to the project folder and execute
Command: ./gradlew packForXcode Now the shared framework should have a xcode-frameworks product and you should be able to build and run the project through Xcode.
This could happen if there are two libraries, where one library was compiled against the different version of the other library than the one currently used in the project. Please check that the project configuration is correct and has consistent versions of dependencies.
I have created new react-native project through terminal.
react-native init PlayWithAnimation
when I run the react-native app through Xcode. I got this error.
/bin/sh -c \"/Users/sumit/Desktop/React\ Native/RNN/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh\"
/Users/sumit/Desktop/React >Native/RNN/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh: line 2: cd: /Users/sumit/Desktop/React: No such file or directory
/Users/sumit/Desktop/React >Native/RNN/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh: line 3: /Users/sumit/Desktop/React Native/RNN/node_modules/react-native/React/scripts/ios-install-third-party.sh: No such file or directory
/Users/sumit/Desktop/React
Native/RNN/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh: line 3: exec: /Users/sumit/Desktop/React Native/RNN/node_modules/react-native/React/scripts/ios-install-third-party.sh: cannot execute: No such file or directory
The following build commands failed:
PhaseScriptExecution Install\ Third\ Party /Users/sumit/Desktop/React\
Native/RNN/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh
(1 failure)
These are the version which I have used:
node v8.0.0
npm 5.0.3
react-native-cli: 2.0.1
react-native: 0.46.0
xcode 8.3.3
I have checked related to other stackoverflow Q & A but did't get proper solution.
Temporary Solution:
It works smoothly if I create react-native with version="0.44.0". But in version 0.45.0, 0.46.0, 0.47.0 builds are failed and same "double-conversion" issue is getting. And one more thing, when I create new project third-party directory is missing.
node_modules/react-native/ (missing third-party directory)
What would be the problem ?
Tried Solution 1:
I did the following steps:
download the files needed inside the .sh, put it in the ~/.rncache/.
copy the downloaded files into node_modules/react-native/third-party/, ran tar -zxf *** to each file.
build again. But not worked.
Tried Solution 2:
Handling third party build error on react-native 0.46x.
and tried with github issue.
I was really excited to finally get started with React Native but this bug absolutely kills my ability to proceed. I'd really appreciate if someone could help me out with this.
Got the solution from jerry han here: The life saver
Hi Bala, As you can see the error log, That error was from ‘WhiteSpace’ on your working path.
Real Path : /Users/sumit/Desktop/React\ Native/
On cd cmd log : /Users/sumit/Desktop/React:
You should rename your working path to ‘/Users/sumit/Desktop/react_native’.
That will be helpful for you.
With developing or operation work, you may be better not to use ‘space’ on the path.
For me, what worked was just updating the Code Signing preference in Xcode to something different and back again.
E.g. I have Automatically manage signing originally turned on. Turning that off and back on again seems to resolve this issue.
I was working through this tutorial, however when I used the react native cli to generate a new project, it would not be able to launch ( with react-native run-ios). I kept getting the above error and I've tried troubleshooting for hours, I think it might be a problem with Xcode as I recently updated it but I'm not sure. Here is the full error message:
Installing build/Build/Products/Debug-iphonesimulator/auth.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/auth.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist
If anyone has encountered this problem and fixed it please let me know what works for you! This has put me at a complete standstill and I would greatly appreciate any help. Could this be a versions issue that react native has not caught up with yet? Thanks!
There is something wrong with react-native init
Please do not initialize the project with react-native init ProjectName
You should append react-native version argument in the end.
For example:
react-native init ProjectName --version 0.44.2
If you are using XCode 10 try downgrading to XCode 9.4.1, by downloading and installing this version in official apple portal.
There might be a lot of possibilities of how to fix it, most of them are clearing npm cache, uninstalling node_modules, deleting ios and android folder and rebuilding, so you should try all of them. But downgrading XCode is what helped me after 5 hours at it
Good luck, don't be discouraged with this error, eventually you will find out the solution!
I keep trying to run my Xcode project (named "ppsideloader") and it keeps giving me 2 errors. Also I Cleaned and Built many times then tried to run, but still same problem.
First Error:
/Users/myUser/Library/Developer/Xcode/DerivedData/ppsideloader-flikuhbwvklweghesxwygrfiylum/Build/Products/Debug-iphoneos/ppsideloader.app/*.dylib: No such file or directory
Second Error:
Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure
My Build Phases:
I don't know what to do, I tried almost everything. Can someone please help me ?
#Emm...I also faced Same Issue. But the issue is fixed when i re install xcode and restarted my machine.
Try the Same i hope that it will be helpfull to you
I get an error when I try to submit app to app store ,the error ocurrs on the last step ( app is being uploaded )
Error : "an error occurred while uploading to the app store"
I doubled checked my certificated and profile and my app configuration on both XCode and iTunes connect.
I tried using the Application Loader but I'm getting the same error
I also tried changing the Java version from 1.7 to 1.6 as many answers suggesting but it didn't work
I'm on Xcode 4.6.2 , OSX 10.8.3 and on java version "1.6.0_45"
Note that when I choose Validate instead of Distribute after archiving the app I get no errors. the error only appears when I try to submit to the app store
EDIT
I restored the Java version to 1.7.0_21 since it seems that the problem is not caused by Java ,
the application loader shows the following two errors in the error log
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter: line 14: awk: command not found
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter: line 18: ../share/iTMSTransporter.woa/iTMSTransporter: No such file or directory
I reinstalled Xcode as a desperate attempt to solve this issue but with no luck
I had exactly the same issue and was able to fix it by slightly adapting the file
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter
change the path to the awk to absolute (and i also uncommented the echo of the script path, which probably isn't necessary). Here my changed file:
#!/bin/sh
# if the user has the run script in their PATH
# then we can get the path to the script from
# 'which'. otherwise, we have to get the path
# from $0
if [ "$0" = "iTMSTransporter" ] ; then
SCRIPT_PATH=`which iTMSTransporter`
else
SCRIPT_PATH=$0
fi
# get the script's directory
SCRIPT_DIR=`echo $SCRIPT_PATH | /usr/bin/awk -F"/" '{print substr($0,1,length($0)-length($NF))}'`
# call the transporter relative to the script's directory
echo Calling: ${SCRIPT_DIR}../share/iTMSTransporter.woa/iTMSTransporter "$#"
"${SCRIPT_DIR}../share/iTMSTransporter.woa/iTMSTransporter" "$#"
I guess this behavior is caused by inproper classpath setup which I wasn't able to resolve though.
After fixing the script, I managed to upload my app through the XCode Organiser.
I was facing the same problem.
I tried many solutions listed on a lots of forums but none of them worked for me.
Here's what I did:
I found Application Loader at /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS
But before that I accidentally ran iTMSTransporter from terminal by using:
"open /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/MacOS/itms/bin/iTMSTransporter"
and it updated by it self. I'm sure whether this was necessary.
Started Application Loader, logged in and selected the ipa file that I had created using Xcode. I started the upload process and it was success.
Now the app is in review. :)
I hope this helps.
Edit: To load Application Loader from terminal use this: "open /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/MacOS/Application\ Loader"
I have tried many methods that were suggested in apple forums and on stackoverflow but non of them worked for me. so I decided to backup my OSx lion and re-install the system all over again.
I know that this might be too radical solution but I had to do it because nothing else worked.