I am trying to build an IOS app with the new VS 2015 cordova addon. I have followed the insturctions on MSDN to install Remote build on my Mac, which seems to work ok.
however, when i tried to build a cordova app from VS 2015 on my PC, i m getting errors, which doesnt give me much info
these are error messages i got from my VS:
Error /Users/[user]/.taco_home/remote-builds/taco-remote/builds/487/cordovaApp/platforms/ios/cordova/build Command failed with exit code 2: {1} D:\[path]\myproject\Error 1
the task runner output in VS:
> cmd.exe /c gulp -b "[project path]" --color --gulpfile "[path]\Gulpfile.js" index
[16:11:19] Starting 'copy-html'...
[16:11:19] Finished 'copy-html' after 4.28 ms
[16:11:21] Using gulpfile
[path]Gulpfile.js
[16:11:21] Starting 'index'...
[16:11:21] Finished 'index' after 9.22 ms
Process terminated with code 0.
and this is what i got from my Mac:
New build request submitted:
/build/tasks?command=build&vcordova=5.1.1&cfg=debug&options=--device&loglevel=warn
{ 'accept-language': 'en-US',
host: '[host]:3000',
connection: 'close',
'transfer-encoding': 'chunked' }
Build will be executed under: /Users/[user]/.taco_home/remote-builds/taco-remote/builds/517
Saving build request payload to : /Users/[user]/.taco_home/remote-builds/taco-remote/builds/517
Saved upload to /Users/[user]/.taco_home/remote-builds/taco-remote/builds/517/upload_517.tgz
POST /cordova/build/tasks?command=build&vcordova=5.1.1&cfg=debug&options=--device&loglevel=warn 202 10663.718 ms - 664
GET /cordova/build/tasks/517 200 0.723 ms - 664
GET /cordova/build/tasks/517 200 2.269 ms - 664
GET /cordova/build/tasks/517 200 1.114 ms - 664
Extracted app contents from uploaded build request to /Users/[user]/.taco_home/remote-builds/taco-remote/builds/517/cordovaApp. Requesting build.
Taking 517 as current build
GET /cordova/build/tasks/517 200 1.320 ms - 11505
GET /cordova/build/tasks/517 200 0.969 ms - 11512
Done with currentBuild. Checking for next build in queue.
GET /cordova/build/tasks/517 200 0.914 ms - 11770
GET /cordova/build/tasks/517/log 200 2.129 ms - -
now from observation, the VS build window shows the failed error message when the MAC terminal windows was displaying "Done with currentBuild. Checking for next build in queue."
I am new to MAC and IOS, so i dont know where to start fixing this problem. Did anyone have this kind of problem before?
thanks a lot in advance
How are you running remotebuild on the mac side? i.e have you got --secure true or false?
Can you post your cordova settings from visual studio?
is there anything in that error file it refers to?
what version of xcode are you using?
Some times while remote building in VS you see errors or warnings but actually it's not that important .
You can just ignore it and open your xcode project in mac_user_name/remote_builds
Additionally check for plugins if they are match to ios platform or not .
Related
in the last days github desktop started alright.
but doday it does not work any more...
most tries the window won´t open and sometimes an empty white window appears
I use Windows 11 but i cannot find out the version number from github desktop because it does not start.
it throws errors in the log:
2022-04-12T19:44:07.014Z - info: [main] Received possible protocol arguments: 2
2022-04-12T19:44:07.015Z - error: [main] Malformed launch arguments received: C:\ProgramData\maxi_\GitHubDesktop\app-2.9.11\GitHubDesktop.exe,--squirrel-firstrun
2022-04-12T19:44:07.027Z - info: [main] Received possible protocol arguments: 3
2022-04-12T19:44:07.027Z - error: [main] Malformed launch arguments received: C:\Users\maxi_\AppData\Local\GitHubDesktop\app-2.9.11\GitHubDesktop.exe,--squirrel-firstrun,--allow-file-access-from-files
2022-04-12T19:44:07.485Z - error: [ui] PullRequestCoordinator: Error loading repositories
2022-04-12T19:44:07.864Z - info: [ui] Subscribed 'Drachenbauer' to Alive channel
2022-04-12T19:45:10.098Z - info: [main] Received possible protocol arguments: 2
2022-04-12T19:45:10.099Z - error: [main] Malformed launch arguments received: C:\Users\maxi_\AppData\Local\GitHubDesktop\app-2.9.11\GitHubDesktop.exe,--squirrel-firstrun
2022-04-12T19:45:10.413Z - error: [ui] PullRequestCoordinator: Error loading repositories
2022-04-12T19:45:10.806Z - info: [ui] Subscribed 'Drachenbauer' to Alive channel
2022-04-12T19:47:08.281Z - info: [main] Received possible protocol arguments: 2
2022-04-12T19:47:08.282Z - error: [main] Malformed launch arguments received: C:\Users\maxi_\AppData\Local\GitHubDesktop\app-2.9.11\GitHubDesktop.exe,--allow-file-access-from-files
my actual repositories are games, that i work on in godot.
https://github.com/Drachenbauer/Sokoban
https://github.com/Drachenbauer/3D-Sokoban
what is wrong here?
What can i do?
Open the github from this url
C:\Users\{username}\AppData\Local\GitHubDesktop\bin\github.bat
this morning I had the same issue and I couldn't make it run, I downloaded again the githubdesktopsetup-x64.exe from the original site, ran it, and now it works again somehow.
I noticed the folder in appdata/local/githubdesktop now only has a folder for the 2.9.14 app instead of like 3-4 folders for other older versions
I realize this post was made a while back, but here's what worked for me if it's still relevant:
Delete GitHub Desktop files from two locations:
Users/-your user name-/AppData/Local and
Users/-your user name-/AppData/Roaming.
Then, remove the program via Control Panel so all the residual files can be deleted.
Then, find the install file for version 2.9.5 from the web. Installing that version worked for me. I hope it works for you as well.
I'm using cloud mac server for releasing in ios. And before changing my mac, i succesfully finished build of my ios app, but then i changed my mac server, now when i try to build, getting error below, what can i do to fix this issue, i tried solutions from duplicates of this error but none of them worked for me.
ERROR
building file list ... rsync: link_stat "/Users/user191346/Desktop/rate_prof/rate_prof/ios/Flutter/App.framework" failed: No
such file or directory (2)
done
sent 29 bytes received 20 bytes 98.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files could not be transferred (code 23) at
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/main.c(996) [sender=2.6.9]
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
I wanna add notification in my app with flutter_local_notifications but once I add the plugin to my .yaml, my app doesn't run again.
Below is the error
```D8: Program type already present: android.support.v4.app.INotificationSideChannel
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/2.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/3.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/6.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/7.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/8.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/9.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/10.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/11.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/12.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/13.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/14.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/15.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/16.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/17.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/18.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/19.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/20.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/21.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/22.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/23.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/24.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/25.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/26.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/27.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/28.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/29.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/30.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/31.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/32.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/33.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/34.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/35.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/36.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/37.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/38.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/39.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/40.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/41.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/42.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/43.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/44.jar, /Users/macbook/AndroidStudioProjects/restaurant/build/app/intermediates/transforms/dexBuilder/debug/45.jar
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: android.support.v4.app.INotificationSideChannel
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 29s
The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See ... for more information on the problem and how to fix it.
Finished with error: Gradle task assembleDebug failed with exit code 1```
Thanks.
First you need to upgrade all the packages that you have to the version where they are compatible with AndroidX. You can know that from the ChangeLog.md of each package on the dart packages page. Next you need to open the android project of your flutter in AndroidStudio, then select Refactor->Migrate to AndroidX. Wait a bit until android studio refactors your project. And the run rebuild project from android studio. It should work then!
I've been building (from a mac terminal) this native application successfully for a long time but today I've run across an error I can't seem to pin down. After tiring from all the javac warnings I upgraded to a newer version of ant. I'm not sure it is related but the timing is suspect. I can still build, deploy, and run my application but now I can no longer use ndk-gdb to debug the native part of the application. It appears on inspection that the gdb.setup file is not getting added to the debug apk.
here is the build sequence, abbreviated output, and information. I'm looking for suggestions on how to resolve the issue.
I've done a full clean on both NDK and ant builds
The android NDK version and android SDK versions are all up to date.
I use the built in ndk-bundle that gets loaded with the android studio sdk tools.
The devices we develop on are not rooted and is not an option.
hsmith$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
hsmith$ $ANT_HOME
-bash: /Users/hsmith/dk/ant/apache-ant-1.9.6: is a directory
hsmith$ ndk-build -j4 NDK_DEBUG=1
[armebi-v7a] Gdbserver : [arm-linux-androideabi-4.8] libs//gdbserver
[armebi-v7a] Gdbsetup : libs//gdb.setup
[armebi-v7a] Install : lib1.so => libs/armebi-v7a/lib1.so
[armebi-v7a] Install : lib2.so => libs/armebi-v7a/lib2.so
[armebi-v7a] Install : lib3.so => libs/armebi-v7a/lib3.so
hsmith$ ant debug
…
-package:
[apkbuilder] Found modified input file
[apkbuilder] Creating -debug-unaligned.apk and signing it with a debug key...
-post-package:
-do-debug:
[zipalign] Running zip align on final apk...
[echo] Debug Package: /Users/hsmith/packageFolder/bin/<package>-debug.apk
[propertyfile] Updating property file: /Users/hsmith/packageFolder/bin/build.prop
[propertyfile] Updating property file: /Users/hsmith/packageFolder/bin/build.prop
[propertyfile] Updating property file: /Users/hsmith/packageFolder/bin/build.prop
[propertyfile] Updating property file: /Users/hsmith/packageFolder/bin/build.prop
-post-build:
debug:
BUILD SUCCESSFUL
hsmith$ adb install -r ~/packageFolder/bin/-debug.apk
hsmith$ ndk-gdb adb --start
ERROR: Package is not debuggable ! You can fix that in two ways:
Rebuilt with the NDK_DEBUG=1 option when calling 'ndk-build'.
Modify your manifest to set android:debuggable attribute to "true",
then rebuild normally.
After one of these, re-install to the device!
I unzipped the apk file to find
unziped apk file/lib/target/
hsmith$ ls -la
total 48264
drwxr-xr-x 12 hsmith staff 408 Aug 25 14:50 .
drwxr-xr-x 5 hsmith staff 170 Aug 25 14:50 ..
-rwxr-xr-x 1 hsmith staff 409940 Jun 3 11:47 gdbserver
-rwxr-xr-x 1 hsmith staff 33920 Aug 25 14:44 lib1.so
-rwxr-xr-x 1 hsmith staff 165092 Aug 25 14:44 lib2.so
-rwxr-xr-x 1 hsmith staff 1614028 Aug 25 14:44 lib3.so
note there is no gdb.setup file
I don't use debuggable=true in the manifest because it isn't needed anymore however including it has no affect on the result.
UPDATE: https://code.google.com/p/android/issues/detail?id=183455
This is exactly the problem I'm having. if you copy the target gdb.setup file from the target directory to the ./lib directory you can get ndk-gdb to work; The COMPAT_ABI variable in ndk-gdb isn't being set correctly and sending the script into a spin. I hope they fix this one soon. almost three days wasted on a broken tool chain.
UPDATE: https://code.google.com/p/android/issues/detail?id=183455 This is exactly the problem I'm having. if you copy the target gdb.setup file from the target directory to the ./lib directory you can get ndk-gdb to work; The COMPAT_ABI variable in ndk-gdb isn't being set correctly and sending the script into a spin. I hope they fix this one soon. almost three days wasted on a broken tool chain.
Machine:Mac
UnityVer:4.6.2
error of the following will appear when you have made a jenkins build of unity.
----- Total AssetImport time: 6.818127s, AssetImport time: 6.808909s, Asset hashing: 0.005416s [60.9 KB, 10.972655 mb/s]
Platform assembly: /Applications/Unity4.6.2/Unity.app/Contents/Frameworks/Mono/lib/mono/2.0/System.Data.dll (this message is harmless)
System memory in use before: 71.7 MB.
Unloading 137 Unused Serialized files (Serialized files now loaded: 0 / Dirty serialized files: 0)
System memory in use after: 66.8 MB.
Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 6940.
Total: 18.863014 ms (FindLiveObjects: 0.248059 ms CreateObjectMapping: 0.096515 ms MarkObjects: 1.745080 ms DeleteObjects: 0.012070 ms)
Scripts have compiler errors.
(Filename: /Users/builduser/buildslave/unity/build/Runtime/Utilities/Argv.cpp Line: 127)
Aborting batchmode due to failure:
Scripts have compiler errors.
Thread 'UnityLookForNewInputDevices' is still running!
(Filename: /Users/builduser/buildslave/unity/build/Runtime/Threads/Thread.cpp Line: 68)
Thread was not cleaned up!
(Filename: /Users/builduser/buildslave/unity/build/Runtime/Threads/Posix/PlatformThread.cpp Line: 45)
FATAL: Unity3d command line execution failed with status 1
Build step 'Invoke Unity3d Editor' marked build as failure
FTP: Current build result is [FAILURE], not going to run.
Finished: FAILURE
Try search "error" in Jenkins console output. It's very easy to overlook what actually causing build fail. The error show in the bottom of console output is the result. The useful information is where all warnings and errors are shown like you normally see in IDE like visual studio. I spend a whole afternoon found out I should always use Control + F instead of my eyes to search through things like Jenkins console output.
The output shows you the problem: you have script errors. Until you fix your script errors, you won't be able to build.
You haven't included the script errors, so no-one can give you any more info. When you fix them, you'll probably find that it's nothing to do with Jenkins, and the question title is unrelated.
Usual causes of this:
You have some editor scripts in you project
You forgot to put #if guards around editor scripts and/or external scripts
You forgot to copy/paste one of your 3rd party libraries or plugins onto the machine where you're doign the build - and it's not in source control already (where it should be).