i've followed this in order to flashbuilder 4.6 to use air sdk 3.4. no problems, or hiccups with the update.
the only problem is when i try to debug a mobile project using this sdk, either for android or ios i get the following error:
Process terminated without establishing connection to debugger.
invalid application descriptor: Unknown namespace:
http://ns.adobe.com/air/application/3.4
Launch command details: "C:\Program Files (x86)\Adobe\Adobe Flash
Builder 4.6\sdks\4.6.1\bin\adl.exe" -runtime "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.1\runtimes\air\win"
-profile mobileDevice -screensize 640x920:640x960 -XscreenDPI 326 -XversionPlatform IOS "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug\teste34-app.xml" "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug"
i've also got this problem.
following is what i've done:
1:create a new empty mobile application and debug it runs
2:open the new app's '{appname}-app.xml' file , find the 'xmlns' property in application root node for example
<application xmlns="http://ns.adobe.com/air/application/3.1">
3:replace the row of your old application
So i think the problem is your air sdk can not support the 3.4 version
Related
After updating to VS 17.3.6 (Xamarin.iOS Version: 16.0.0.72) I'm getting the following error when trying to build the app for the Simulator. It does work on a physical device.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(3,3): Error: No matching framework found inside '/Users/xxx/Library/Caches/XamarinBuildDownload/FAdM-8.13.0/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.xcframework'.
SupportedPlatform: 'ios', SupportedPlatformVariant: 'simulator', SupportedArchitectures: 'i386, x86_64'.
I've tried deleting the obj and bin folders.
How can I solve this issue?
I used to be able to run on android and all of a sudden I am getting this error (see below).
The only thing I recall changing is downgrading "nativescript-ui-listview" to "^7.1.0" and "nativescript-ui-sidedrawer" to "~7.0.0" because it otherwise breaks on ios 12.
Webpack compilation complete. Watching for file changes.
Webpack build done!
Project successfully prepared (android)
Installing on device f180a829...
More than one .apk found in /Users/manuelmaestrini/Programming/spiio-development/spiiomobile/platforms/android/app/build/outputs/apk directory. Using the last one produced from build.
Successfully installed on device with identifier 'f180a829'.
Application com.spiio.mobile is not running on device f180a829.
This issue may be caused by:
* crash at startup (try `tns debug android --debug-brk` to check why it crashes)
* different application identifier in your package.json and in your gradle files (check your identifier in `package.json` and in all *.gradle files in your App_Resources directory)
* device is locked
* manual closing of the application
Unable to apply changes on device: f180a829. Error is: Application com.spiio.mobile is not running.
Any idea what might be? I tried to do --clean, remove node_modules, hooks, platforms, uninstall and reinstall webpack etc but no luck...
I can't get a simple app to run on watchOS 3 and it's driving me CRAZY!
I'm running with Xcode 8.
Recreate scenario: Create a newiOS app (defaults to deployment target 10), add WatchOS project (3.0). Try to compile.
I get:
Could not AOT the assembly (MT3001)
Changing Build link to "Don't Link" on all three projects and downgrading to target 8.4 and Watch OS 2.2 results:
Error MT1006: Could not install the application on the device: Sent message error( error : 0xe800002d).
Changing to target 10, but keeping Watch OS 2 finally gets compiled and installed on the phone and deployed on device, but debugger either:
A. Never manage to connect over Wifi to the watch (stuck at "waiting for the app to connect on port 10000)
B. Get the following error:
Launched watch application 'com.XXX.testwatch.watchkitapp' on 'Apple Watch' with pid 270
Exception: Xamarin.Hosting.MobileDeviceException: Send Message Error (error: 0xe800002d)
at Xamarin.Hosting.RealDevice.StartSession () <0x118c24dd0 + 0x0009d> in :0
at Xamarin.Hosting.DebugService+c__AnonStorey6.<>m__0 (System.Object v) <0x118c24450 + 0x000cf> in :0
[MVID] 703d5be3b466420882f6cb97c41b6723 0,1
What am I doing wrong here?
I've submitted a bug report To Xamarin. They confirmed. You need to modify the default compilation to disable the incremental build.
I built the Tizen sample application in wearable IDE 2.3.1 and 2.3.0. I was able to run it on the emulator. But the same application is not installing on my 2.3 wearable target device. While installing, it gives errors. I tried the procedures below for installing the application.
* sdb install app
* wrt-installer -i app (For installing web application)
These are the error messages I got:
E/WRT_INSTALLER( 513): pkgmgr_signal.cpp: setPkgname(164) >
[SECURE_LOG] name is empty
D/WRT_INSTALLER( 513): task_configuration.cpp: hasExtension(85) > [SECURE_LOG] Looking for extension .xml in
/opt/home/developer/WearableUI.wgt
D/WRT_INSTALLER( 513): widget_unzip.cpp: getDecryptedPackage(265) > [SECURE_LOG] Check DRM...
D/WRT_INSTALLER( 513): widget_unzip.cpp: isDRMPackage(171) > [SECURE_LOG] Enter : isDRMPackage()
E/WRT_INSTALLER( 513): widget_unzip.cpp: isDRMPackage(180) > [SECURE_LOG] Cannot open /usr/lib/libdrm-service-core-tizen.so!
I have one more concern: Is the libdrm-service-core-tizen.so library required for installing applications on Tizen? (For now we are using software rendering.)
Are there any command line tools for installing Tizen native/web apps?
This log is not enough to know the exact cause. WRT installer is to continue the installation regardless of the existence of the .so file. I think that will have more direct cause behind the log. Find and send more log.
I am using Xcode version 5.0 and trying to use instruments,when i am running the script which contains "var target = UIATarget.localTarget();"
the following error appears :" Could not start script, target application is not frontmost."
It's known issue:
The message “Could Not Start Script : Target app is not frontmost” may be displayed when attempting to capture a UI Automation script in Instruments against the iOS 7 Simulator.
If this occurs, close the trace document and create a new one. 15387075
Source: Xcode 5.0.2 Release notes