Jamcast

Hi Phil,

Thanks for reporting this. As I mentioned via email, let's reset this issue if you don't mind so we can build it back up with hopefully me getting a grasp on things this time. Time to squash this one for good.

The only current known cause of this issue is uninstalling the Android app and reinstalling it, this causes a new unique app ID to be generated and therefore requires a new authorization. If you go into Jamcast Server Manager, click the Devices tab, you can right-click and Forget All Devices. Then perform some browse action via the Android app and you'll see a new Android device appear in the device list. Go ahead and right-click this new item and approve for remote access. You should be good to go at this point in time; let's leave the Android app in place for the duration of this troubleshooting period so we are sure not to have to re-authorize.

I remember you saying that you use this a lot from the office -- can you perhaps say with any certainty that this authorization issue occurs only at work? The theory here is a proxy server in your work environment is stripping the necessary HTTP headers from requests coming from the device, which would essentially prevent the Jamcast authorization scheme from working properly.

Those are my thoughts for now -- let me know what you can add to this after you've used Jamcast for a day or so and run into the problem again.

Thanks!