I a developing a mobile app and i am getting this build error when try to launch the app on ios simulator. Much appreciate that if someone can help me figure this out.
[ERROR] ** BUILD FAILED **
[ERROR] The following build commands failed:
[ERROR] CopySwiftLibs /Users/shenalvanderwall/Documents/Appcelerator_Studio_Workspace/appforusers/build/iphone/build/Products/Debug-iphonesimulator/appforusers.app
[ERROR] (1 failure)
Process exited with 1
app was perfectly running till yesterday.
I figured it. The problem was with the Titanium SDK. I downgraded it from 9.3 to 9.1.
Now it is working. The error was Titanium SDK was damaged somehow.
Related
We upgraded the mobile development project we are working on to React Native v0.70.3 from 0.66.4 and our build starting to give all sort of issue in our build server after that. Both iOS and Android builds are failing with following error messages.
Android:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':react-native-camera-kit:verifyReleaseResources'.
A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
Android resource linking failed
ERROR:/Users/jenkinsoffshore/CICDBuilds/workspace/Mobile-Service-Android/node_modules/react-native-camera-kit/android/build/intermediates/merged_res/release/values/values.xml:2784: AAPT: error: resource android:attr/lStar not found.
iOS:
iOS build ends in success and we can upload to testflight as well. but getting the following error in email and the app crashes in devices.
ITMS-90863: Apple silicon Macs support issue - The app links with libraries that are not present on Mac:
#rpath/hermes.framework/hermes
After you’ve corrected the issues, you can upload a new binary to App Store Connect
We upgraded the MacOS version to Ventura and Xcode along with in the build machine. In developer machine both builds work fine.
Do we have to do anything specifically after upgrading to React Native 0.70.3?
Downgrade to atmost react-native 0.69
Rebuilding the server completely solve the issue. We had to setup everything from scratch. There must be a simple solution that that but project deadlines made us to go for a full re-inttall.
i try to open the Android app in Nougat 7 or above android version but there is a error show in appium, the error is bellow.
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Command failed: Failed to install C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]\r\n)","killed":false,"code":1,"signal":null,"origValue":"Command failed: Failed to install C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]\r\n"},"sessionId":null}
info: <-- POST /wd/hub/session 500 7986.817 ms - 520
So, Please Suggest me how to solve the session null issue.
Note: the same code is run in android OS 6 Marshmallow, 5 Lollipop.
The issue you are facing was fixed in recent Appium server release 1.7.1.
In change log under Android section you will find
Add support to force upgrade settings app
So your steps now:
Update appium server: npm install appium#1.7.1 -g
Rerun your test
Try uninstalling the app manually if it already exists on the device. If it does not, try an erase/reset of the device itself. I've run into upgrade/overwrite issues in the past that were resolved by cleaning up the device.
I have tried to build a react-native app using react-native-navigation. I've went through all the setup stages, but when I try and run the app, I get the following error:
** BUILD FAILED **
The following build commands failed:
CompileC /www/MyProject/ios/build/Build/Intermediates/ReactNativeControllers.build/Debug-iphonesimulator/ReactNativeControllers.build/Objects-normal/x86_64/RCCNavigationController.o RCCNavigationController.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Any idea what can be causing this?
I thought i was the only one getting this error bro.
After upgrading to react-native 0.31 today, react-native-navigation was having problems. It was working just fine before.
Adding runtime header wouldn't solve the problem. It would let the build go through successfully but the build crashed on me in runtime.
I'm currently considering rebuilding scene transition entirely using react-native-router-flux.
I have suddenly started getting worklight build errors like below. I have no clue why it started happening suddenly. The code was working fine until the remote machine I use for Xcode builds was rebooted. Any clue what could be causing it ?
ipad build failed: Failed initializing ClientProjectBuilder
android build failed: Failed initializing ClientProjectBuilder
iphone build failed: Failed initializing ClientProjectBuilder
Regards
Avi
The solution to this error, typically, is to delete the wlBuildResources folder, located in the TMPDIR of the OS.
See here: Worklight - FWLST1040E: android build failed: java.io.FileNotFoundException
Close Eclipse
Locate your temp folder (Windows, OS X)
Delete the wlBuildResources folder
Open Eclipse
Re-build
It may be helpful to also delete the native folder before closing Eclipse, however do note that if you have written custom native code you should first back it up so it won't be lost(!).
I am using Titanium Studio, build: 3.1.3.201309132423, Titanium Mobile 3.1.3.GA SDK and iOS7 SDK
My console has been acting weird where when I compile, I get this message:
[ERROR] : An error occurred running the iOS Simulator
[ERROR] : [DEBUG] using retina iphone retina tall ios 7
[ERROR] :
[ERROR] : Project failed to build after 21s 326ms
Yet the project did build and compile and launch in the emulator just fine. The problem with this is now any of my debugging properties that I output to the console, I cannot see because Titanium Studio thinks the app never ran so it isn't listening anymore.
I did notice that after I build and compile again, I can see all my previous debug statements in the console. It's like the console is one build behind or something. Is anyone else have weird issues like this?