Process Stopped Unexpectedly.

Get Started | Login

Discussion Forums > Android Studio, Errors, Installing, Configuring

Replies: 3 Views: 74

sonicshrimp Apple Fan Posts: 5 Reg: Nov 13, 2012 Oxford 4,050	confirm \| cancel 09/24/13 11:04 AM (12 years ago) Process Stopped Unexpectedly. I am having a nightmare with eclipse. I know nothing about code but managed to get a good app onto the app store using buzz touch. I gave up with android after a frustrating month of nothing working and decided to have a go this year..... I'm up to date with my SDK and eclipse. I can get my virtual device to work and I've changed nothing on my control panel but I just cannot get my app to work on android! I'm using pdf plugins. I've followed the instructions.pdf to a tee but nothing would launch. I was getting 'multiple dex' errors until Ideleted a duplicate .jar file and now the emulator tries to launch the app until I get this new error: "The application FitToDrive (process com.fittodrive has stopped unexpectedly." Log cat says: 09-24 18:59:36.772: E/AndroidRuntime(454): FATAL EXCEPTION: main 09-24 18:59:36.772: E/AndroidRuntime(454): java.lang.NumberFormatException: Invalid int: "1.0" 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.invalidInt(Integer.java:129) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parse(Integer.java:366) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parseInt(Integer.java:357) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parseInt(Integer.java:323) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.fittodrive.BT_screen_splash.onCreateView(BT_screen_splash.java:89) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:735) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:926) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.BackStackRecord.run(BackStackRecord.java:578) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1226) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:374) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Handler.handleCallback(Handler.java:587) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Handler.dispatchMessage(Handler.java:92) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Looper.loop(Looper.java:132) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.ActivityThread.main(ActivityThread.java:4025) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.reflect.Method.invokeNative(Native Method) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.reflect.Method.invoke(Method.java:491) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599) 09-24 18:59:36.772: E/AndroidRuntime(454): at dalvik.system.NativeStart.main(Native Method) That seems to be the end of it. Most users of my medical app use android and it would be a shame to have to leave it again but I feel a bit at sea with this. Any help would be appreciated? Title Comments I am having a nightmare with eclipse. I know nothing about code but managed to get a good app onto the app store using buzz touch. I gave up with android after a frustrating month of nothing working and decided to have a go this year..... I'm up to date with my SDK and eclipse. I can get my virtual device to work and I've changed nothing on my control panel but I just cannot get my app to work on android! I'm using pdf plugins. I've followed the instructions.pdf to a tee but nothing would launch. I was getting 'multiple dex' errors until Ideleted a duplicate .jar file and now the emulator tries to launch the app until I get this new error: "The application FitToDrive (process com.fittodrive has stopped unexpectedly." Log cat says: 09-24 18:59:36.772: E/AndroidRuntime(454): FATAL EXCEPTION: main 09-24 18:59:36.772: E/AndroidRuntime(454): java.lang.NumberFormatException: Invalid int: "1.0" 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.invalidInt(Integer.java:129) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parse(Integer.java:366) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parseInt(Integer.java:357) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.Integer.parseInt(Integer.java:323) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.fittodrive.BT_screen_splash.onCreateView(BT_screen_splash.java:89) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:735) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:926) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.BackStackRecord.run(BackStackRecord.java:578) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1226) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:374) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Handler.handleCallback(Handler.java:587) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Handler.dispatchMessage(Handler.java:92) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.os.Looper.loop(Looper.java:132) 09-24 18:59:36.772: E/AndroidRuntime(454): at android.app.ActivityThread.main(ActivityThread.java:4025) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.reflect.Method.invokeNative(Native Method) 09-24 18:59:36.772: E/AndroidRuntime(454): at java.lang.reflect.Method.invoke(Method.java:491) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841) 09-24 18:59:36.772: E/AndroidRuntime(454): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599) 09-24 18:59:36.772: E/AndroidRuntime(454): at dalvik.system.NativeStart.main(Native Method) That seems to be the end of it. Most users of my medical app use android and it would be a shame to have to leave it again but I feel a bit at sea with this. Any help would be appreciated?

Masons App Design Aspiring developer Posts: 206 Reg: Aug 06, 2013 Andrews, TX 12,660	09/24/13 11:24 AM (12 years ago) What does it say in your console when this happens? Comments What does it say in your console when this happens?

sonicshrimp Apple Fan Posts: 5 Reg: Nov 13, 2012 Oxford 4,050	09/24/13 11:30 AM (12 years ago) Nothing at all: console and error log empty. Comments Nothing at all: console and error log empty.

Paul Rogers Android Fan Posts: 2524 Reg: May 30, 2011 UK 35,740	09/24/13 04:42 PM (12 years ago) There's an invalid integer. Integers are whole numbers, but somewhere in your control panel you've entered a setting as '1.0' - maybe in the splash screen transition duration? Comments There's an invalid integer. Integers are whole numbers, but somewhere in your control panel you've entered a setting as '1.0' - maybe in the splash screen transition duration?

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.