Jump to content

jbrodriguez

Community Developer
  • Posts

    1,947
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by jbrodriguez

  1. v2.1.0 has been submitted to both stores. This release enables support for over-the-air updates, to remove dependency on App Store submission, for critical bug fixes. Look for a Settings icon colored red, to know that an app update is available. Restart the app to apply the updates. Also in this release: - Fix a bug where servers with an incomplete parity check couldn't be added - Add support for unRAID mainline releases, such as 6.2.1-20160922 - Restore access to Open Source Libraries screen - General improvements Starting with this release, 'patch' (2.1.x) versions needed to fix critical bugs, will be delivered over the air, to minimize deployment times. 'minor' releases (2.2.0, 2.3.0, etc) will be delivered using standard App Store / Play Store submissions. But I could still make an exception to this general rule. Thanks for all the support and patience with the app's growing pains
  2. That probably explains my problems too. Confirmed.. also my issue... I also found a workaround: start a parity check and then add the server... Worked on first try ! That's good to know Helmonder, the next release will have a fix for this, so there'll be no need for the workaround
  3. Kudos speeding_ant ! Your app was a source of inspiration !
  4. Hello all, v2.0.4 is available for iOS. Nevertheless, it's missing a couple of fixes. As interwebtech mentioned, I found a bug using his server's data, it's related to the server having an incomplete parity. This is fixed. 6.2.1-xxxxxx can't be added, this is fixed. CHBMB brought up a valid point about mainline releases. I'll write about it later. I'm also working on distributing 'patch' releases over-the-air (both iOS/Android), which should speed up store process considerably (especially App Store). I'll post back soon.
  5. Hi jonathanm, that's a nice idea ! I'll look into it.
  6. Is this why its not working with mainline? Hi gridrunner, I'll check this ... didn't realize there would be a mainline version so soon.
  7. Thanks peter_sm ! Could you try changing font size in the app settings ? Let me know if that makes a difference.
  8. Hi, I've published v2.0.4 to App/Play Store ( normal submission times apply on the App Store, for the time being ) The connection logic was modified to make serial calls to the server, rather than in parallel. This should help prevent bottlenecks in the server (hanged connections). Also: - Timeout settings should be saved now - A bug with stop array setting was fixed as well To obtain server/dockers/vms info, the app was making many calls in parallel. To make it easier on the server, each call is now sequential, so connection/refresh/etc could be a little slower (although I didn't notice differences with my servers). Hope this solves some of the issues.
  9. Hi itimpi, it should work. At the moment, I'm changing a bit how the apps connects to a server, I think that should solve the issues when adding a server.
  10. Yes, I'm changing a bit how to connect to a server, I should have that ready by tomorrow the latest.
  11. Right, due to the settings bug, it wasn't actually changing the timeout.
  12. Well, I did misname two variables so the timeout settings weren't being saved Stop array confirmation had an issue as well, which is fixed now. I changed the server press behaviour on Android, I think it should solve that issue. I'll look into the issue of adding servers now.
  13. Ouch ! I didn't make that many core changes since the last version, and settings was definitely not one of them Thanks for the reports, I'm running some tests.
  14. Hi interwebtech, what strikes me as odd is that the settings do not stick. That's a very simple operation, shouldn't be an issue. In any case, can you try setting manual timeout to 0, then add the server manually ? I had a very busy weekend (couldn't touch ControlR) and I'm getting up to speed with some test data I got these past few days. Timeout setting does not save. Is there supposed to be a "save" button? I don't see one so I assume going back to previous is supposed to save any changes made? I tried manual add (again) and doesn't find it. This time it just goes direct to "no server available" screen with no scan run that I can see. I killed an app I suspect is messing with my VPN. Now automatic scan stops on correct IP .8 but is just spinning. Never completes. Oddly enough it defaults to IP ending in .22 when doing a manual scan. My server is on .8. Just thought it odd it defaults to that number. No, there's no save button. It should save them as soon as you change any settings. It defaults to the device's address, not the server's I'll pm you to get a bit more data to debug.
  15. Hi glave, it gets the ip from the unRAID environment, not sure if something changed in v6.2. But as rmeaux mentioned, you can always type manually the url (ipaddress:6237) In any case, I'll look into the issue.
  16. Helmonder, try one thing .. set manual timeout to 0, then add it manually. If that doesn't work, I'll pm to go a bit deeper into the issue.
  17. gridrunner, I had a similar report and got some test data, eventually I'll send you a pm, to ask you the same. I'll post back my findings soon.
×
×
  • Create New...