i am trying to publish an ios application using adobe flash cc on mac and flash professional cs6 on windows.
when i publish my application using cs6 ( air sdk 3.7, air sdk 3.6 ) on windows ipa is created and installed only on jail-break phone and when i try to install jailed phone its simply shows application failed to install.
when i start to publish with flash professional CC on mac (Size of Ram is 768MB) ipa is not created but the following errors are shown:
"Restore windows
The application “java” unexpectedly quit while trying to restore its windows.
Do you want to try to restore its windows again?"
and
"ADT quit unexpectedly while using the libjvm.dylib plug-in.
Click Reopen to open the application again.
Click Report to see more detailed information and send a report to Apple."
and at last a error report
if anyone face this issue or have sorted out this please let me know.
thanks
Virender
Error report:
Process: java [1175]
Path: /usr/bin/java
Identifier: net.java.openjdk.cmd
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: sh [1174]
PlugIn Path: /Applications/Adobe Flash CC/Adobe Flash CC.app/Contents/jre/jre1.7.0_10.jre/Contents/Home/lib/server/libjvm.d ylib
PlugIn Identifier: libjvm.dylib
PlugIn Version: ??? (???)
Date/Time: 2013-07-11 22:10:34.716 -0700
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report: 37146 sec
Crashes Since Last Report: 41
Per-App Interval Since Last Report: 6085 sec
Per-App Crashes Since Last Report: 41
Anonymous UUID: CDBA110A-A463-40BB-9E1F-2321B9E94AFE
Crashed Thread: 18 Java: Java2D Queue Flusher
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000003b0
VM Regions Near 0x3b0:
For a quick solution you can try using IfunBox with install IPA on a non jailbreack phone. By the way i had the same probrem, I was unable to instal my IPA on a non Jailbreack phone but wen i upload to Apple every thing goes fine! One of the reasons of the intalation fail could be that u didnt mach the license id and software name wen um create the IPA.
Related
Every time I run my project (macOS Cocoa App) I get this message in the Xcode console:
Message from debugger: unable to attach
I have already tried creating a new project (error still occurs), changing some „Signing settings“ (as mentioned in "Message from debugger: unable to attach" when running Tests on OSX app) and reinstalling Xcode.
Xcode Version: Version 10.1 (10B61)
OS: 10.13.6 (High Sierra)
Model identifier: iMac12,2
We have been developing for Gear Fit 2 during the last 4 months using Tizen Studio 1.2 and haven't have any problems with CERTIFICATES until the 8th January 2018, when we received the update to Studio 2.1.
Now it's impossible to install any of our Apps to the Gear Fit 2 because we get an installation error in the Wristband (CERTIFICATE_EXPIRED).
All the GEars have the updated Firmware (R360XXU1DQE6) and we have reinstalled Tizen Studio 1.2, 1.3 and 2.1 and generated CERTIFICATES with the corresponding Certificate Manager tool in each release of Tizen Studio. Also we have made a Factory reset to all the units we are using for our project(15xGearFit2).
We have obtained the same error using all the releases of Tizen Studio in MACOS 10.10.5 and Windows 10.
The error we get for all the apps a we have tried (include the samples included in Tizen Studio) is:
[Deploying the package...]
RDS: On
[Creating the package...]
Created the package: /Users/delacal/workspace/BasicUI/Debug/org.example.basicui-1.0.0-arm.tpk
[Transferring the package...]
Transferred the package: /Users/delacal/workspace/BasicUI/Debug/org.example.basicui-1.0.0-arm.tpk -> /opt/usr/apps/tmp
[Installing the package...]
Uninstalling the package...
path is /opt/usr/apps/tmp/org.example.basicui-1.0.0-arm.tpk
start process (install)
.
error : 34
end process (fail)
processing result : CERTIFICATE_EXPIRED [34] failed
spend time for pkgcmd is [3578]ms
cmd_ret:34
(7.407 sec)
Has any pleople the same problem?
Thank very much in advance.
According to this link, this issue occurs due to date & time mismatch between PC and development device. Updating date and time on device is supposed to solve this.
My iOS app built in Visual Studio with a Xamarin Mac build host runs on the iOS simulator but does not deploy to the device. The Mac server log shows this:
[2013-07-30 13:28:45.7] Handling with command: [Build: CommmandUrl=Build] (20)
[2013-07-30 13:28:45.7] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-07-30 13:30:56.4] Error: Failed to acquire command execution log, the request timed out
[2013-07-30 13:30:56.4] Command [Build: CommmandUrl=Build] finished (17)
Incidentally, is that a typo in line 3 - shouldn't it read "lock" not "log"?
We are using Xamarin Studio 4.0.10 (build 7), Xamarin.iOS 6.4.0.2 (Business Edition), XCode 4.6.2 (2067.2) Build 4H1003.
What is the cause of this error, and how can we get past it?
After talking with Xamarin folks I was told that a fix was included in the Beta for Xamarin.iOS 6.4.1. I switched my Xamarin Studio to the Beta Channel (via the update dialog) and am now able to deploy as before.
I have installed the latest version of ADT (Android Developer Tools Build: v21.1.0-569685) and eclipse 3.8. I followed the instructions (http://developer.android.com/training/basics/firstapp/running-app.html#Emulator) to start the Hello World example but the AVD crashes on start, with no error messages in the console.
I tried that and even lower RAM to 40M but still no luck. I tried all kinds of combinations of RAM and resolution (lowered resolution to 480 x 800 hdpi), camera settings, enabling "Run as Admin". It just crashes w/ a message "emulator-arm.exe has stopped working". The console doesn't show any error message.
I have tried many solutions that came up on Google but no dice; plus a lot of them are very old posts. Please help!
Please see screen shot of my configurations and crash message here:
http://imgur.com/a/mvogh
My machine:
Win 7 64
RAM: 8GB
Processor: AMD Phenom(tm) II X6
Graphics card: ATI Radeon HD 5450
This is what I see when it crashes:
emulator-arm.exe has stopped working
problem details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: emulator-arm.exe
Application Version: 0.0.0.0
Application Timestamp: 5111a505
Fault Module Name: atioglxx.dll
Fault Module Version: 6.14.10.9232
Fault Module Timestamp: 4b208022
Exception Code: c0000005
Exception Offset: 0000b212
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I tried running "adb logcat" and screen said "waiting for device". I started Eclipse and started AVD from AVD manager. It crashed again but "adb logcat" still said waiting for device.
Is it possibly a hardware issue?
Thanks.
I installed latest driver/software from ATI and everything worked. Thanks.
If you need to debug any given Android instance, from both real devices or from the AVDs, use adb logcat, other than that, your question it's really without any specific detail that can help with this.
I have a weird problem since a few days. After exporting a project for android once it works fine the 2nd export I do eclipse crashes with this error:
Identifier: org.eclipse.eclipse
Version: 3.8 (3.8)
Code Type: X86-64 (Native)
Parent Process: launchd [269]
Date/Time: 2013-03-12 21:36:13.365 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 321292 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 44806 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 52A136CA-CDAE-4661-B166-51B04A18C21C
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x000000011f1c965f
Crashed Thread: 46 Java: ModalContext
Any clues. Running: adt-bundle-mac-x86_64-20130219
SIGBUS looks like bad RAM but then other things would act up aswell?
B
I guess that's random. As mentioned in this thread it looks like it can happen if eclipse is building your project at the same time as you're exporting it. You could try to disable the "build automatically" option in eclipse while you're exporting it.