I'm developing a SQLite-heavy Windows Phone 8 application and tried to use the latest version, which however seems extremely buggy and randomly fails during INSERT and UPDATE statements with zero-explanation errors (see SQLite 3.8.2 exception on Update statement). For that reason I removed the latest version from the project and entered the one that works correctly.
I published the app to Windows Phone Store after rigorous testing, everything working correctly. However, when it came out, the errors that happened when the newer version was there are happening again. I tested the exact same Release build XAP on my device (via the Deploy tool), and it works perfectly. But after I download the app from Store, once again I get the same issues.
Has someone a way to explain these problems? I repeat, that the exact same XAP that I uploaded I tested and it is working.
EDIT: Additional note - the problems are really random - the same INSERT once works and doesn't another time, although data are valid...
Thank you very much, I'm quite desperate...
The new version of SQLite (3.8.3.1) that was released on 11th April 2014 should resolve any issues, finally :-) . So far I have not encountered the same error again so I suppose it is now fixed.
http://www.sqlite.org/releaselog/3_8_3_1.html
Related
While I am aware that Hot Restart is in preview, it was for quite a while now and my testing never really worked since the first time I've tried it. I've waited for a few VS studio versions to come up, hoping that my issue will be fixed. Since I've kept an eye on issues and haven't seen something similar, I tend to believe that the issue is locally with my setup.
Here is the situation:
I've enabled Hot Restart in VS and added my account, picked the team (after I was added) and everything went fine without errors. I have a free apple account, but after I was added to a Team I was able to obtain automatic provisioning to work.
I've tried to set the debug build options similar to how the simulator was set
I've disabled device specific build as I saw in the docs that it can create problems.
I've installed iTunes just as specified in the docs and when I connect my device to my Windows 10 PC, I can select it from the list.
So basically it looks like everything is set up. I use for testing an iphone 7 with latest iOS version.
Here is what happens:
I've selected different types of output logs hopeing to catch some error in there that could lead me to find a solution.
when starting to build I can see "Building offline for a local device" and I can see my provisioning file details on "Detected signed identity"
I see no apparent error while it compiles and does its job, no complains about signing
then it gets to the IpaCopyToStagingDirectory and there it starts to copy a bunch of files from bin\Iphone\Debug to Artifacts\app.iOS.dSYM where I get the final error: Could not copy the file bin\iPhone\Debug\\app.iOS.ipa because it was not found
If I go to the bin folder, there are many files, including app.iOS.exe, but indeed there is no ipa file. I also don't know why it has two \ on its path.
Any ideas why is not working?
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1
By some mysterious reasons I got myself a jailbroken iPhone 3GS from a vendor whom I am finding difficult to track.
My task is to test out in app purchase functionality on it.
Currently it has iOS 5.0.1 with cydia installed.
No, it does not have Appsync.
I am installing my build through testflightapp API which works without issues with my app so far.
However when I initiate in app purchase, I don't get anything in response.products so far.
I have added productIDs and all in itunes-connect already, checked twice that they are fine, since 48 hours.
I tried testing with iPhone simulator 5.1, but all I got was no values from storekit. I would love to hear if there is any workaround with simulator.
Worked around this finally - deleted my app from itunes connect, re-added it.
It complained about name being already used.
I changed the language of name. And it worked.
Maybe, my prior app setup was right, but I had something else messed up.
In between, I rejected my app. That maybe one of the reason behind this issue.
Lesson?
Don't developer reject your app.
Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message "error: Failed to attach process to id " is displayed, being different each time. Attempting to 'Stop' the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the 'Home' button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing 'Product->Attach to process.'
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn't help. I reinstalled Xcode, didn't help. I upgraded to 4.4.1 Aug 7, didn't help. I deleted all trace of Xcode data, running: find / -name '[xX]code' and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn't work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I've tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single 'Label' object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
xcode-4-4-ios-5-1-simulator-problems
crash-of-xcode-4-4-for-mac
failed-to-attach-to-process-id-xcode
unit-test-target-doesnt-run-on-xcode-4-5
xcode-4-4-freezing-on-project-close
simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I've spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I'm not going to specify all the build info, just because it's whatever comes stock on the fresh install of Xcode.
I had similar problem (although with different configuration) and found incredibly simple solution by chance. I just used Product->Stop, then Product->Run (through keyboard shortcuts if that matters). Just once! Then the problem disappeared.
configuration: XCode 4.2, iPhone Simulator 5.0
symptom difference: process attaching didn't fail
It seems to me that the problem stems from the XCode-Simulator communication, and that's why I've shared my experience here despite the differences.
EDIT: It comes out Stop; Run didn't provide permanent solution for me. The problem is recurring from time to time. Still it is a temporary workaround for me.
I got this a few times, especially when I kept running my app and cancelling it or interrupting it too often, it's not something you can put your finger on, but yes I always managed to get back up and running by deleting the app in the simulator, cleaning project and build folder, deleting derived data (in Xcode organiser > projects view), restarting simulator and Xcode.
This also happened a few times on the device, and I needed to restart the device, iPhone in my case. I hope these infos help you out.
I got this to work by building and running the simulator using the Xcode 4.5 developer preview. I then closed it out and reopened Xcode 4.4.1 and it built and ran fine.
While none of the solutions above worked for me, thanks for putting this all together. I figured I'd answer here since this was the most comprehensive.
While this isn't exactly a solution, after today's OSX 10.8.1 update from Apple, this issue has been resolved. It's safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.
I think I've cracked this one for my particular case, and I admit it's somewhat a mistake only newbies should do but I had overrided
viewWillApear:(bool)animated {}
in a ViewController of mine, without calling back
[super viewWillApear:animated]
It might be a good idea to search for all view lifecycle methods in your project and see if you have similar problem.
Does any else have a problem where when using VS2005 or VS2008, it suddenly 'forgets' to color code and format the text for you? All of a sudden it acts like its a plain old notepad editor. Sometimes if I save and re-open the file, or else re-start Visual studio altogether, it suddenly 'remembers'. I thought maybe this was because of a bad install on my machine, but recently upgraded to a new one, brand new fresh install with all service packs - and we are right back to the erratic behaviour....
Is this a known problem? Is there a workaround (i.e. a key combo I can hit to tell it to do its thing?)
PS: This happens for me when doing asp.net with VB code - not sure if it affects other flavors of the tool...
EDIT: This is a clean install of VS2008 on Vista, but also have had it on XP. No addins on either setup, problem happens routinely.
Sometimes something similar to this happens to me in VB.Net. In my case it has alway been the backgroundcompiler service that has stopped working for one reason or another. Haven't found anything that helps besides restarting visual studio.
I got this often when working on large web projects (> 1K pages and 4K total files) and most often on ashx files.
At the same time, I would lose intellisense, This was happening because the files I was adding were not getting marked as "Compile" in the file properties -> build option.
I never found the cause (assumed it was overburdening the solution) but I found that it would stay fixed for longer if I deleted the SUO file periodically (it was getting into the 1MB range).
Since coming to a new company, new PC, etc, I have not had this problem but then again I'm not working on as large of a web project.
I use C# in VS2008, and haven't had any problems. Maybe this is VB.NET related?
I used to see the problem with "Web Sites". I have since changed most of my projects to "Web Applications" and haven't seen the issue in a while.
I had a similar issue with VS 2003. I use VS 2008 right now and this doesn't happen anymore.