@matigo I think that would be praised as a bold design move by the tech douchebags should any company start doing so.
@c Nope. Just introducing an enhancement to an existing ”feature” of the app that has triggered a lot of feedback.
I find it oddly satisfying to design features that are backwards transparent. The users of the older version do not get the feature but the app just keeps on working. Also, switching the thing on remotely is just pure magic.
(Edit: found -> find. What the fuck was I doing when I wrote that?)
@streakmachine Just wait for the winter. Then you can enjoy the sunrise while having lunch. Also, you get to see the sunset at the same time. If it isn’t cloudy, obviously. ?
@matigo This problem could have been avoided if the gomobiletool would not have suppressed the actual error message. Also, it could use the absolute path to the Android SDK tool it uses internally because it was initiated with the path to the SDK.
Problem solved. I had to set my PATH to include the tools of the Android SDK tools. So yeah, the error message did not tell that.
gomobile: no Android NDK path is set. Please run gomobile init with the ndk-bundle installed through the Android SDK manager or with the -ndk flag set
Guess what I have done? Fuck you, Google, get your shit together…
After I had cleaned up that Android/Scamsung shit I managed to encounter another pile of shit produced by Go and its gomobile tool. Sigh…
@matigo The documentation says that the service stuff will be run in a worker thread, but apparently on this Android device it is run on the main thread. Yay. Not.