How to Read App Save Data Usb Debug

Debugging Applications

1. Last updated

2. Save as PDF

Template:OutSystems/Documentation_KB/ContentCollaboration

Edit

Debug your app in Service Studio by pausing the execution at breakpoints, specific points in a module, and so running the logic step-by-stride. This lets you find whatsoever bug in your logic design.

The Debugger tab shows app information like variable and runtime values. It also shows the current debugging context (current thread, event name, UI flow, screen and activity, when applicable. Utilise the debugger commands available in the Debugger Toolbar and in the Debugger carte du jour.

How to debug your app

To debug your app, do the post-obit in Service Studio:

1. Click the 1-Click Publish push to relieve the latest changes in the module before debugging.

2. Fix one or more breakpoints in the module y'all're debugging.

3. Before debugging a native mobile app, choose a debugging target in the Debugger tab: Android, iOS, or Google Chrome which emulates a device. The section Mobile Debugging Scenarios includes further details near the different targets. If y'all're debugging a mobile app distributed as a PWA, select Emulate using Google Chrome in Debugger > Debug Setup.

   

4. Start debugger by clicking the Showtime Debugging button in the Debugger tab or by selecting Debug in the Public Surface area in the Debugger menu. When you're debugging mobile apps using the Google Chrome target, Service Studio opens a dedicated Chrome browser example for debugging only.

   Note: To also open a browser when starting a debug session in a web application, bank check the Open in new browser window selection in the Debug Setup tab.

   

5. Practise some tasks in the module, upward to a point when the execution runs into a breakpoint and suspends.

6. When y'all switch to the Service Studio window, the menstruum or screen containing the chemical element with the breakpoint shows on the canvas. Service Studio selects the element with the breakpoint and marks is with the debug icon.

7. The execution context shows in the Threads tab of the Debugger tab, marked with the electric current thread icon, showing the electric current execution stack of the module elements. The Debugger tab also shows additional information you can explore.

8. After analyzing the runtime values at that execution point, y'all tin can go on running the app by:

   • Selecting one of the commands available for advancing the execution of the awarding logic: Go along, Footstep Over, Step Into or Step Out. The execution bespeak advances according to the command you run.

   • Right-clicking an element on the canvas (or in the module tree) and selecting the Continue To Here choice in the context card. The execution continues until it reaches that element on the canvas.

In some scenarios you demand to debug some functionality exposed by some other module (called a producer module).

While developing Traditional Web apps y'all tin can likewise debug modules in your Personal Expanse. This lets you test your changes separately from other developer's changes in the same module.

Mobile debugging scenarios

There are different ways of debugging a mobile app that help you detect, understand, and fix issues. You tin debug your mobile app in i of the following ways:

Emulate the mobile app using the Google Chrome browser in your PC

Use the Chrome browser in your PC to debug your mobile app if you lot don't demand to execute native plugins, as the native plugins can't run in PC. This option is convenient to test the logic of the app. However, to bank check the performance or experience of the mobile app, test your app on a real device. Besides consider this scenario if all the native plugins in the mobile app accept activeness wrappers defined that return mock data when the plugin isn't bachelor. For more information, check the Best Practices topic on creating wrapper actions for native plugins.

Install the Mobile App on a Device

Test the mobile app straight on a device as your users would run it. It'southward the best identify to test the performance and experience of your app. You tin practice it in an iOS or Android device. Generate the native app package for your app in Service Studio using the Debug (Android) or Development (iOS) build type, install it in the device, and follow the steps below according to your mobile device platform.

To examination a mobile app on an iOS device:

1. On your PC, install iTunes.
2. In your device, turn the "Web Inspector" selection on. For detailed instructions run across Troubleshoot Debugger Connexion Problems.
3. Connect your mobile device to the PC through a USB cablevision.
4. In your device, allow the PC to debug on the device.

To examination a mobile app on an Android device:

1. In your device, turn USB debugging ON.
2. Connect your mobile device to the PC through a USB cable.
3. In your device, let the PC to debug on the device.

For more assistance, check Troubleshoot Debugger Connectedness Problems.

If you need to troubleshoot app crashes, a plugin or check the native code of apps, debug your apps with the mobile platform's native tools, such equally Android Studio for Android and Xcode for iOS. Before debugging using the native tools, you must generate a mobile parcel with Debug (Android) or Development (iOS) build type.

Working with dates and times

When debugging an app and checking the values of the Date Time data blazon, proceed in mind the following:

• During debugging, Service Studio shows UTC engagement and time in the debugger.
• In the client UI, the engagement and time are in the timezone of the client.
• On the server, the date and time are in the timezone of the server.

Yous tin read more nearly timezones in Available Data Types.

Articles in this Section

• Breakpoints

  Breakpoints are used to suspend the execution of your awarding while troubleshooting and debugging issues.

• Watches

  Utilise watches to examine module elements while debugging threads in your module.

• Threads

  Learn more about threads in OutSystems.

• Public and Personal Areas

  Larn more about the two areas where modules can be executed and debugged.

• Debugging Producer Modules

  Check how to debug functionality exposed by a producer Module being consumed in a different module.

• Debugger Tab Reference

  UI reference for the Debugger Tab in Service Studio.

• Troubleshoot Debugger Connection Bug

  Troubleshoot issues that can arise while connecting your mobile device to your PC for debugging purposes.

sisemorevaust1993.blogspot.com

Source: https://success.outsystems.com/Documentation/11/Developing_an_Application/Troubleshooting_Applications/Debugging_Applications

Share this post