Versions Compared

Old Version 6

changes.mady.by.user Vikas Verma

Saved on

compared with

New Version 7

changes.mady.by.user Aaron Culliney

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

NOTE: Local Development Server feature is available in the Pulsar for Salesforce 3.8 pre-releases for Android and Windows. Some of the features listed here may change before official release.

Debugging your HTML/Javascript code in Pulsar doesn't require you to upload a bundle to Salesforce servers.  With some configuration, you can instead have Pulsar load directly from a local development server on your own development machine.

...

  • pulsar.developer.enableDevelopmentServer – Pulsar Setting must be set to TRUE

  • pulsar.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!

...

  • First make sure your local development server (HTTP only) is running on port 3002 of your development machine. (Verify in your browser that you can reach http://127.0.0.1:3002 – NOTE of course that Javascript calls into Pulsar will fail when your server is accessed from your browser).

  • For development with Pulsar on Windows, you must be running the Pulsar app on the same Windows machine as your local server. You will also need to ensure that the Pulsar app is has loopback exemption:

    • CheckNetIsolation.exe LoopbackExempt -a -n="E3D1A000.PulsarforSalesforce_ta6n8xy84gcpg"

    • Verify that Pulsar is showing in the exemption list: CheckNetIsolation.exe LoopbackExempt -s

  • For development with Pulsar on an Android device, you must have that device connected to your development machine via ADB (either USB cable or via network) with reverse port forwarding set up.

    • Your Android device must have Developer Options and USB Debugging enabled

    • Set up reverse port forwarding from your development machine: adb reverse tcp:3002 tcp:3002

    • Note that the ADB client/server can sometimes gets disconnected (and the reverse rule purged).  You will need to recreate the rule after re/connection to the device. You can double-check that you have reverse port-forwarding of 3002 in place: adb reverse --list

...