...
With Pulsar running on Android and Windows, you can debug your HTML/Javascript code from a local server running on your own development machine. This productivity feature allows you to bypass the time-consuming process of uploading a new .pulsarapp bundle to Salesforce servers and resyncing the Pulsar app.
| Anchor | ||||
|---|---|---|---|---|
|
pulsar.developer.enableDevelopmentServer– Pulsar Setting must be set to TRUEpulsar.developer.users{.DocId}– List of developer usernames (e.g., you@yourorg), separated by comma, semicolon, or newlines for a specific document. Note that {.DocId} can be empty, in which case this is an org-global list of developers (for all documents!)We recommend that you only have these setup for your testing orgs, and never for your production orgs!
...
Debugging your Javascript running in Pulsar
Debugging on Windows
...
If you prefer debugging with log statements, you have direct access to the Pulsar logs at the following location on disk: C:\Users\<YourUserName>\AppData\Local\Packages\E3D1A000.PulsarforSalesforce_ta6n8xy84gcpg\LocalState\Library\Application Support\log.txt
On Windows Pulsar versions before 11.0.0.0
...
, you can fully debug your Javascript running in Pulsar by using the Edge Developer Tools. Video link: Video - Debugging on Windows
New for Windows 11.0.0.0+ -
...
use Edge Browser Developer Tools: With Pulsar version 11 on Windows, you should debug your code using the built-in Edge
...
browser developer tools, which will be
...
available for any user/document combination authorized for local development server use (via pulsar.developer.users{.docId} setting). The older Edge Developer Tools preview application will no longer work with Pulsar. To
...
use the built-in Developer Tools
...
...
with Pulsar, be sure to enable remote debugging (click to see Microsoft documentation). In summary :
Enable Developer Mode: Open Windows Settings, select Privacy & security > For developers, and then turn on the Developer Mode toggle.
In the same Settings page, turn on the Device Portal toggle (follow prompts to install developer packages if necessary).
After the installation is complete, note the Device Portal URL that will be used for the remote debugging connection. To find this URL, expand the Device Portal dropdown on the same Settings page, and a list or URLs will appear. Choose the local URL, for example,
http://localhost:50080.In the Chrome browser, navigate to the following URL:
edge://inspect.In the Connect to a remote Windows device text box, enter
http://<Device Portal URL>, such ashttp://localhost:50080, and then click Connect to Device.Ensure that Pulsar has loaded the content you wish to debug.
Verify that you can successfully connect, and a section named Edge is listed. Click inspect to load the DevTools window and debug your content:
...
Debugging on Android
On Android, by design, Google fully restricts access to embedded WebViews running in released apps. What this means is that you cannot attach a debugger to the Pulsar app to debug your Javascript.
...