1

Github project is at https://github.com/GarthSmith/WindowsTwitterShareTestApp2016 with an appxbundle available here.

This app crashes on my Lumia 929 phone with Windows 10. Clicking the share button runs DataTransferManager.ShowShareUI(). Waiting on the Twitter login screen will then crash the app.

It does not crash if I have a debugger attached. It only crashes on my ARM phone with no debugger attached.

  • How do I debug this crash?
  • How can I capture this crash for reporting?
Vadim Kotov
  • 8,084
  • 8
  • 48
  • 62
Garth Smith
  • 103
  • 7
  • 1
    I guess that this may be a [problem in suspending event](http://stackoverflow.com/a/24103734/2681948) - to debug it use lifecycle tab. – Romasz Apr 28 '16 at 21:31
  • 1
    I tested your project in Lumia 950, OS Build:10586.218 Version:1511 and it works well. I don't have a Lumia 929 phone, but you may try to test your project in other devices to see if it still has the same problem. – Jay Zuo Apr 29 '16 at 07:01
  • @Romasz thank you for pointing this out! I did not know about this. Unfortunately, firing the suspending event did not seem to cause the crash. – Garth Smith Apr 29 '16 at 19:49
  • @JayZuo-MSFT Thank you for checking this. I did a factory reset of my Lumia 929, built 10.0.10586.218, Version 1511, and it still is crashing. Testing on another Lumia 929 also crashed. I am getting some more devices tonight to test some more. If the app says "No clicks yet" after logging into Twitter, that means the app has crashed and been restarted by the OS. I will update the project to make it more obvious. – Garth Smith Apr 29 '16 at 20:11
  • I tested it on my Lumia 1320 with 10586.242 (Release Preview Ring) and after clickon on share and selecting Twitter, the Twitter App starts fine. I see no crash. – magicandre1981 Apr 30 '16 at 06:41
  • 1
    I don't think this is a crash anymore, but my misunderstanding. From the [documentation on the Application.Suspending event](https://msdn.microsoft.com/library/windows/apps/br242341): "The Suspending event is the only indication your app will receive prior to termination (if it happens). Because of this, you should store enough session state (such as the current article being read or the current movie playback position) to recreate the exact same experience during activation." – Garth Smith May 02 '16 at 06:24

0 Answers0