Jump to content

Custom version (0.517)


Recommended Posts

cragjagged
Posted

 

 

Question is, why is the http not returning 200 when it works for the vast majority...

 

 

 

 

I'm on the alpha version of the server, might be related to the below 

 

  • Api now supports requests without /mediabrowser prefix. You'll notice a shorter url now when opening the dashboard from the tray icon.
Posted

<p>

 

I'm on the alpha version of the server, might be related to the below

 

  • Api now supports requests without /mediabrowser prefix. You'll notice a shorter url now when opening the dashboard from the tray icon.

By Alpha, do to mean Dev?

 

I'm always on Dev server release.

cragjagged
Posted

By Alpha, do to mean Dev?

 

I'm always on Dev server release.

 

Yes that's what I meant! Sorry still have work speak in my head!

  • Like 1
Posted

I was on Dev also......just gone back to Beta and the Samsung app now works :-)

chessdragon136
Posted

Confirmed - Upgraded to Dev and experiencing the same issues. 

@@Luke FYI please read the last few posts, it looks like the changes to the URL have broken the app and to my knowledge I don't believe I'm handling anything wrong. 

Posted

the server still supports requests that use /mediabrowser, for full backwards compatibility. from the logs above the url's appear to have /mediabrowser/mediabrowser

Posted

Confirmed - Upgraded to Dev and experiencing the same issues. 

 

So is this purely an issue installaing the app whilst on the current DEV server ??

 

As I said, I have been on DEV since MB3 was first released and I'm not seeing an issue.

chessdragon136
Posted

Sigh @@Luke I hadn't spotted that. But glad you're aware of the issue now.

chessdragon136
Posted

Try v0.526 I've just pushed out and see if that helps. I've locked this now for the sake of my sanity trying to keep up and as I believe the issue is fixed

  • Like 2
Guest
This topic is now closed to further replies.
×
×
  • Create New...