You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have previously (years ago) successfully used RunnerUpLive on/to my own server, but am unable get it working today. It appears the reason is that the client software does not even attempt sending any requests to my server. Dunno if it is due to the functionality having becoming rotten, or if modern android simply blocks web requests unless one taps down a hundred levels into the app permissions or whatever?
Tested on two different android devices, running 2.6.0.2 on the first device and 2.5.2.0 on the other. Both installed from f-droid.
When launching a run after having populating the username, password and server address no requests to my server happens. There are no errors in the android app, nothing appears in the access log and collecting pcaps from my wireless router tells the device is not even attempting to make a single request.
Neither live reporting nor explicitly clicking "LADDA UPP (1)" generates any http requests.
Unfortunately I do not currently have adb installed nor developer mode enabled for any of my current devices and can't easily debug any further.
Is this known and expected behaviour? Can it be reproduced, or is it perhaps a user mistake on my side?
The text was updated successfully, but these errors were encountered:
I do not know about any RU Live users and have never tried it myself.
I believe there were some additional setting required for RU Live, do not see it right now.
There are no "Android level" settings what I know.
Some changes have had to be done to RU Live due to Google requirements when updating (handling foreground services etc), those have not been tested so it may be that this does not work. (and upload should be disabled for RU Live).
I have previously (years ago) successfully used RunnerUpLive on/to my own server, but am unable get it working today. It appears the reason is that the client software does not even attempt sending any requests to my server. Dunno if it is due to the functionality having becoming rotten, or if modern android simply blocks web requests unless one taps down a hundred levels into the app permissions or whatever?
Tested on two different android devices, running 2.6.0.2 on the first device and 2.5.2.0 on the other. Both installed from f-droid.
When launching a run after having populating the username, password and server address no requests to my server happens. There are no errors in the android app, nothing appears in the access log and collecting pcaps from my wireless router tells the device is not even attempting to make a single request.
Neither live reporting nor explicitly clicking "LADDA UPP (1)" generates any http requests.
Unfortunately I do not currently have adb installed nor developer mode enabled for any of my current devices and can't easily debug any further.
Is this known and expected behaviour? Can it be reproduced, or is it perhaps a user mistake on my side?
The text was updated successfully, but these errors were encountered: