Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 23565 [details]
VSFM prompts an error message when Mac >Unified API ScenKit, Sprite Kit app is run in the debug mode in simulator and stop icon is clicked
Bug Test env -https://gist.github.com/gangrade-swati/ae2dc231df24b69638ba63d1cf8ddbe1
Repro Steps -
1. Launch VSFM
2. Create Mac >> Unified API >> Xamarin.mac SceneKit Game and
Mac >> Unified API >> Xamarin.mac SpriteKit Game
Mac >> Unified API >> Xamarin.mac Cocoa
3. Select Configuration sa Debug
4. Click on Run icon
5. Application gets deployed successfully on simulator
6. Click on Stop icon
Actual Result - VSFM prompts an error message as “Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.”
Please attach logs / stack trace. We've had many false positives from QA on scenekit bugs before.
Logs are attached with the mentioned gist link - https://gist.github.com/gangrade-swati/a73eb92e213b07d67f88b0b46552cab4 contains the error message displaying in exception pop up. Please let me know if any other data is require
Is there any output in the application output tab? Can you run it from the command line and get me the standard out.
It appears to be a mono abort, but I can't tell just from the stack trace. The IDE logs do not help.
Also, can others reproduce this or is it isolated to your machine?
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!