Page Comparison

...

• First make sure your local development server (HTTP only) is running on port 3002 of your development machine. You may wish to use or extend the simple example server scripts that are published in https://github.com/luminixinc/PulsarForSalesforceJSExamples. Once the server is running, verify in your browser that you can reach the server at http://127.0.0.1:3002 – (NOTE of course, that Javascript calls into Pulsar will fail when your server is accessed from your browser).

  • NOTE: If you are building a React or Angular app to run within Pulsar, these frameworks already have an HTTP server component for your app during the development process, you just need to make sure the port is set to 3002 so that Pulsar can reach it. Again, make sure you can reach the http://127.0.0.1:3002 location from your desktop browser first, to verify the server itself is working!

• 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 has loopback exemption:

  • Local development server must be running on the same Windows machine as

  • 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 emulator or device, you must have that device connected to your development machine via Android Debug Bridge – ADB (either USB cable or via network) with reverse port forwarding set up.

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

  • Your development machine (can be macOS, Linux, or Windows) should have Android Studio (or at least the CLI tools, in particular ADB) – https://developer.android.com/studio#downloads

  • 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

...