This has been working for me in the past 2 years -- and all of sudden stopped working. Opening the Monitor always occurs at the default 9600 baud.
I tried uninstalling and reinstalling PlatforIO ... but to no avail.
Is there an additional setting that may be corrupt?
Has anyone seen this issue before?
Simple Blinky test
So if anyone ever stumbles on this ... It was fixed in the last Platformio update ...
Related
I was changing some stuff around in my app and tried to re-run it and all of a sudden I get a ton of errors in the console that don't really make any sense. Does anyone know what's going on here? How do I fix this?
Solution: Restart XCode... it had to install some stuff so that it could run. sigh
after working on an app for quite a while all that's left now is improving startup timings - and the given solution for that is Webpack.
Using npm run start-android-bundle produces an app that works as intended (with some minor problems with firebase).
But using npm run start-ios-bundle produces an app that starts with the splash screen and then only shows white. Unlike other problems here on StackOverflow it doesn't just need a few seconds on the white screen but the starting component never shows up, without throwing an error.
Has anyone encountered the same problem or has an idea how to fix this problem?
Many thanks to Nick Iliev for looking into the matter. The problem was in the Firebase-plugin and has been addressed here: https://github.com/EddyVerbruggen/nativescript-plugin-firebase/issues/564.
Updating nativescript-plugin-firebase should fix the problem
I've got a real head scratcher here. I just upgraded to Xcode 7.3.1 and all my Bots have hit the floor during the integration process. For some reason or another the Bots get stuck on step 7 of 9 "Processing results". I let it sit for about 24 hours to see if it would work itself out but had no luck.
Anyone ran into this problem and have any idea what a fix might be? Short of reinstalling Xcode and Server on the build server, I'm not sure what else to try as I've tried a lot of random fixes that I've seen out on the interwebs.
Thanks in advance for any help?
UPDATE - The last thing to run in the raw build log is:
Test Suite 'All tests' failed at 2016-05-19 13:32:16.765.
Executed 131 tests, with 1 failure (0 unexpected) in 4.500 (4.592) seconds
Update: Fixed
Here's what I did:
Stopped the server.
deleted all bots from Xcode.
Went into /Library/Developer/XcodeServer and removed (you will need Admin access):
Logs
Integrations
Removed my derivedData directory
Restarted everything and rebuilt the bots using different names for them.
I had the same problem once. I think it happened after updating Xcode. Only solution was to reinstall OS X. After that I have not had any problems. I tried everything I could find from the web but there weren't any solutions out. I tried to delete everything that belongs to Xcode but I think I didn't find all of them. So my suggestion is to reinstall OS X. Copy all your important stuff to external hard drive or to cloud.
I know this is not the suggestion or answer you are looking for but it helps you out.
I have tried deleting my derived data and restarting Xcode, and it works for a few seconds, until the Indexing is complete and then it's broken again.
Does anyone have any recommendations on how to fix this?
I searched in the apple developer forums and there are a lot of other users having the same issue. They say to go back to a previous version of Xcode 6 but I don't know where to find one, so any advice on that would be much appreciated as well.
I never realized how much I rely on Code Completion, I am pretty much stuck until I get this fixed.
PLEASE HELP!
This issue was resolved by upgrading to Xcode6.1.1
I'm experiencing a very confusing issue with Xcode. It started when the debugger started skipping over some lines and stopping at the wrong lines on breakpoints. I tried adding NSLogs, but they weren't having any effect.
I restarted Xcode and did a clean build, and now no breakpoints fire anywhere, and NSLogs don't work either, even in -applicationDidFinishLaunchingWithOptions:. I've made sure that the current scheme is in Debug mode, so I don't know why this would be happening.
Has anyone else experienced something similar?
EDIT: Logs that were present before I started having this issue still work, but no new ones.
#Jumhyn, You should write the solution then by yourself and accept that answer and close it or accept this answer saying ... TRY TO RESTART YOUR COMPUTER :)