Is there any up to date doccumentation for debugging and viewing the error log?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • I huge amount of my time and energy is being wasted because all of my searches for what should be simple questions result in posts and threads that are years old and obsolete or misleading.

    The current simple info I can't find is where do I find the error log after my app crashes?

    I got no useful answer when I asked for clear documentation for setting up the emulator or troubleshooting when it doesn't run, but I discovered I can plug in my phone via USB and choose build and run and it will try to run on my phone but a message appears saying "sorry, app couldn't start" but now I have no idea where to find the error log so that I can try to figure out why it's failing to open.

    Any help or direction towards non 2015 instructions for using the Android exporter would be greatly appreciated.

  • Quote

    I discovered I can plug in my phone via USB and choose build and run and it will try to run on my phone

    Not sure what you mean by "discovered", AFAIK this is explained in the CF 2.5 documentation.

    Generating log files didn't change for a long time. Open your Android SDK directory, go to the Tools sub-directory, run monitor.bat and then select your device, you'll see the log.

    Lines that contain MMFRuntime are written by the Fusion runtime. When you get a crash you get a MMFRuntime line that also contains "exception" and the next lines are the call stack at the time of the crash.

  • Note: you can also generate a log with adb. Open a command prompt window in the platform-tools subdirectory of the Android SDK, and enter this command:

    adb logcat

    If you want to save the log to a file:

    adb logcat >filename.txt

    Other info in this post:

    Please login to see this link.

  • Thanks for the info Yves.

    Regarding my frustration with not finding info easily, my instinct was not to go into Fusions built in manual for instruction for the Android exporter DLC, I think many/most people these days, especially those of us who choose a tool like Fusion because we don't want to spend hours in pages of text and type out real code and worry about typos and syntax all the time to get anything done will look at the sticky posts in the forum thread dedicated to the exporter and the store page of the product for links to concise tutorials (especially videos or tutorials with clear screen grabs) and fast-help guides. These sticky posts exist, but they are not well updated and have obsolete and misleading/time wasting info/instructions right up-front, like telling us on the very first post we need to install both the java sdk and the android sdk, yet 20 pages of replies later you might find out that's no longer the case and android studio auto-installs the java sdk.

    Then once you find the documentation there are many very logical places where the critical information for what the error log is and how to use/access it would fit perfectly and be extremely helpful, but those handful of sentences to explain it are not there.. Maybe they are there somewhere, but I've not found it, and it was glaringly missing in the several spots it should have been, near making builds, testing, and trouble-shooting I kept asking myself "Why is this critical info not here?"

    Since those sticky threads already exist and are right on top, I highly recommend quick edits to fix these issues and right up front to remind people of the built in documentation in Fusion and let them know that's always the best place to get the most up to date info, even for the DLC add-ons (if it is), It still tells us to install both the java and android sdk as of today I think.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!