I'm about to lose my mind.
Yesterday I was working a bit to get some ads in my app, which I'm trying for a long time, since there is -no- good tutorial that clears out easily on how to put them.
Anyway, yesterday I wanted to close my pc, and I got blue screen, for those who know, it's announcing a crash of your pc.
I shut down the pc manually, and at the restart, I cleaned the pc (dutch: "schrijfdefragmentatie') twice.
After that, I wanted to open Eclipse, and I got many, many errors, about Parser exception for /MainActivity/AndroidManifest.xml: Premature end of file.
and that about all my apps.
I'm trying to open AndroidManifest.xml, which gave a red error-icon, but now it's totally blank!
As for my src\com.example.appname\MainActivity.java, it's also blank !
I fear that I've lost my app due to this.
Though, I got my app on my cellphone (Android).
Can I get that version back on my pc? Because this has the only relevant code and stuff.
Or is there another way to save my app?
Related
The app I have created seems to open quite slow (and janky) compared to other apps on my phone. It only seems to happen on android
I have tried copying the dependencies to a new project and running it and it doesn't replicate the same behaviour.
I have also changed the original app to only load a red container in the matierial app but its still really choppy on app launch before it loads.
I would post some code but I am not entirely sure whats wrong.
Sorry this is quite vague but I am running out of ideas. I dont really want to have to recreate everything in a new project.
Please note I have done the android v2 migration so it could potentially be linked to this?
Does anyone have any ideas to what could be causing it?
Update:
Forgot to mention this is on profile/release mode.. its not debug mode causing it
Well, it's hard to know why your app is being so "janky" but i'm going to make a few shots in the dark:
Are you running this on an emulator or on a real phone? Emulators will sometimes act weird, and will deliver results that you might not see on an actual android device. If you are running this on an emulator, try launching it on a physical phone. I have had experience with using Android emulators and sometimes trying to open the app at all becomes weird. How old your phone is might also be the cause of this, if it is old.
Do you have too many tabs open? Try exiting out of all of your applications and then open up your flutter app. See if that does anything.
That is all that I have concerning the environment that you are working in. You haven't posted any code, so i'm going to have to ask you about what your app is doing on startup. It would be good if you posted some code or a link to a git repository so that I can see that and be of better help.
The Problem:
Until recently, I could build and test my app like normal. Now, Xcode is driving me crazy, I can't even run my app.
-
What Happens:
Building my app seems to launch it in the simulator, but it does not run and an EXC_ARITHMETIC error occurs (it stops at a line of code that was working fine before, no code changes since).
Looking at the 'products' folder, I can see that "appName.app" is red - i.e. the app file is never generated. A spotlight search and checking in the build folder confirms this.
Cleaning, restarting, etc does nothing to help. Other projects still build fine.
-
When it happened:
One of the graphic files I altered wouldn't update itself in the app, even after a 'clean'. So I deleted the build folder, as I've done many times before. Now I get the result explained above.
-
Any ideas or solutions are much appreciated!!! I can't develop as is... and have already wasted a lot of time as is. I'm more than happy to give a bounty if someone finds a good way to fix this, it's driving me crazy!
I had a similar problem too when my app always crashed at launching, sometimes it helps to delete the App from the Simulator. Simply hold the mouse on the app for some seconds, click on the X, close the simulator, rebuild and run.
Solution was to comment out the block of code that the error occurs in. Build, and then it runs fine.
Then, uncomment the same block. Build, and works fine.
Weird... compiler or maybe Xcode bug?? Feel free to try explain...
I have an iPhone app that I'm trying to run on my phone via Xcode.
It installs and runs without an issue
I make a change in the source code (negligible, like an NSLog())
It installs without an issue
Running causes the error:
Error Starting Executable 'myApp'
Don't know how to run. Try "help target".
I uninstall the app, and reboot the phone
It installs and runs without an issue (until I make another change; then I have to repeat this dance)
Needless to say, having to uninstall the app, reboot the phone, and reinitialize the environment (i.e. set prefs) takes an unreasonable amount of time, and is probably indicative of a serious problem. The issue is, the only vague error message I receive gets me nowhere on Google. Where on earth could this issue be coming from?
With some help from #iphonedev, I figured it out. Turns out it's a glitch in iOS 5 beta. The way to fix it is to remove the device from Development Devices, then re-add it.
Yeah just restarting the iPhone with the lock and home buttons fixes this. Had it happen a few times to me
I'm not a developper, but a user of an iPhone (3GS, iOS 4.1, Jailbroken) which started to crash randomly last week on several app. If I'm right, it crashes randomly when I tap on the keyboard (texting, sending an email, search on Google...), so that's why the crash happens on several app I guess.
By crashing I mean:
- Either, the app close itself (Safari.app, Mail.app...)
- Or, the SpringBoard crash and the iPhone go on SafeMode
What I did before it started to crash:
- Weeks ago, I installed a Cydia Tweak to setup a Frecnh Keyboard, tweak I uninstalled after it started to crash, thinking it was because of it, but apparently it wasn't
- I installed a .deb manually with Cydia, everything went well
- I modified the /dpkg/status file in order to prevent Cydia from asking me for an app update, everything went well too (besides some description line which I had to delete)
Here are 2 Crash Log:
http://pastie.org/private/nuncku1absv3frk5f4tva
http://pastie.org/private/1lc9lfbhdagkynhsmwm6w
=> They talk about UIKit, does anybody know what is wrong and what should I do to fix the crash? I tried to look for on Google, bu I didn't find anything unfortunately...
Thank you very much for your help!
Thomas
Correct answer:
Get the package "Crashreporter" from Cydia (BigBoss Repo).
For Springboard crashes, you can ignore the warning at first start.
Select the most recent crashlog, wait a moment for the analysis.
The most likely suspect for the crash will be displayed first.
Get rid of that package, and retry.
Here's the situation:
-Had a development build of the app we just submitted on my phone, working fine for days (and previous builds worked fine for weeks).
-Yesterday, I touched the app icon, the app launches then crashes out (I wasn't connected to my computer at the time, but if I had to guess, it was around or before when applicationDidFinishLaunching runs). Basically, I briefly see my Default.png, then the app closes. This happens every time I try to run it.
-I restart my phone. No difference, the app is still failing to launch. All other iphone apps I have appear to be working fine.
-This morning I reinstall the app from my development computer and all is well, it's working fine again. No problems. This is the SAME EXACT CODE with the same build parameters.
This has me really worried, does anyone have any idea at all what might have happened? It's like the app permanently broke itself, before it even hits any of my code no less :(. I had a theory it might have had to do with an expired provisioning profile, but I didn't get any message then or when I reinstalled.
I'd appreciate any advice/pointers/ideas people have!
Connect your iPhone to the computer, launch XCode, go to the Window menu, and select Organizer. Click on your device in the left hand bar, and check your crash logs.
That should tell you when it is crashing, and why.
Actually, the crash logs should still be there from when your app WAS crashing, so even if you have reinstalled, you may be able to figure out what WAS going wrong.
Are you using core data?
Did you change your schema? That would cause a crash on startup and a reinstall would then fix it.
If it was the exact same code it seems to point to a data issue.