My Wear Watchface occasionally crashes (App has stopped message on my Moto 360). This happens when I'm not around a PC to check the current logs through ADB.
Is there any way to automatically save log files when a crash occurs on Android Wear, and to retrieve the log files later?
Related
I use console to track device logs. At work I've connected many co-workers phones to Xcode and have since removed them from the Device and Simulators window. However, those devices are still appearing in Console and when I select them I am able to see their logs.
How can I remove these devices?
I have a published Mac app which uses Core Data and I am in the beginning stages of implementing iCloud (Documents) to sync data between devices (using Ensembles). When I attempt to turn on iCloud the app does not run. It builds successfully and then says it has finished running. This message appears in the Console:
Message from debugger: unable to attach
If I turn off the iCloud capability it will run successfully with no issues.
I am logged into iCloud, and there are no issues shown in the setup. Any ideas as to why I cannot use the iCloud capability? The same issue occurs if I try to activate Push Notifications (even with iCloud Off).
iCloud Settings 1
iCloud Settings 2
Up until today, I've been able to build, run, and debug my watch app and iOS app at the same time. When I build and run, the debugger attaches to the watch automatically. Then I have to manually attach the iOS debugger. I have been following these steps and they always worked perfectly. I can hit breakpoints on both on the watch and the phone (which is what I need to do to be able to debug things like sendMessage or applicationContext).
The problem now is that when I go to attach the iOS app to the debugger manually (via Debug -> Attach to Process), it doesn't show up in the likely targets or in applications at all, even though the app is running on the phone.
I checked my schemes and made sure that the targets were still correct- they are.
I even tried Debug -> Attach to Process with PID or Name. When I try to attach the iOS app by name, I get an error saying Will install Watch App called with bad bundle identifier '(null).
Why is my iOS app no longer a likely target? How can I get it to attach to the debugger again while my watch app is also attached?
I use another way to debug on watch app and iPhone app at the same time. I run this script when watch and iPhone simulators are running on my Mac. Then launch my watch app or iPhone app on the same simulators. I can observe both log at the same time.
P.S. These log are come from console, so you should use NSLog(), not print().
I'm focusing on the new Test Flight procedure. I developed an application (that I submitted through Xcode to the iTunes Connect portal) that crashes if a UIButton is tapped. Since, the application is available for Beta Testing to Internal Testers, I would expect to see a crash log within the new Crashes section of Xcode 6.3 Beta 4 (see Crashes Organizer Help). But nothing. No crashes available.
Is there any particular reason for that? Is this related to the type of testers I'm using? I'm understanding that Xcode 6.3 is Beta version.
Update
Xcode 6.3 has been released and crashes are now available.
Original answer
From Apple documentation
How Crash Logs Are Collected and Aggregated into Crash Reports
Apple provides a service that collects crash logs from users and
organizes them into downloadable crash reports. However, crash logs
are collected only if you upload an app with the symbols. (In the
Archives organizer, select the “Include app symbols for your
application…” box when you upload your app to iTunes Connect.) For
apps released in the App Store, the user must also agree to share
crash logs with developers. TestFlight users automatically share crash
logs with developers. The service that creates the crash reports does
the following:
Collects crash logs from both TestFlight and App Store builds
Provides the total number of unique devices where the crash occurred
Provides a sample set of crash logs for each crash report
Removes all personal user data from the crash logs
Creates crash reports daily
When you open the Crashes organizer, Xcode begins refreshing the crash
reports for your apps. Xcode downloads the top crash reports—crash
reports with the most number of occurrences on unique devices—that
occurred during the past two weeks. However, there may be up to a
three day delay between when you first distribute your app and when
crash reports are available in Xcode.
where emphasis is mine.
So I guess I need to wait.
When you submit a new build to iTunes Connect you will see THIS screen in organizer and you need to make sure the box is checked that says:
"Include app symbols for your application to receive symbolicated crash logs from Apple. "
When setting up an iPhone up for the first time you are asked THIS
If you select "Don't Share" then the crashes won't be reported
P.S. I tried to show images in the post but I don't have any rep yet so it wouldn't let me, the best I could do was link to some images.
Can you get an iTunes Connect crash log when you download your app from the App Store and then build on that app using Xcode?
Let's say I have a released version, and I download it from the app store to test, then later on I want to make some changes to my code.
I don't delete the downloaded app, but I just build over it from Xcode. Then I add a lot of breakpoints during the initial launch to check. Suddenly, my app crashes because it isn't able to launch in time.
Will the crash be sent to iTunes Connect?
Also, it is possible for your app to fail launching when you have a lot of break points added and you try to step into things?
I'm using Xcode 4.6.
Once you run your app from Xcode, your app is no longer the same app. It is now your development app. If it crashes, nothing is sent to iTunes.
When you run your app through Xcode, the timeout is disabled. You could let it sit for a week and the OS will not kill it for taking too long to startup.
And I believe you mean "iTunes Connect" where ever you mention "iTunes".