Sseason Finals - Feedback

[regrbde]

This weekend we had our big season finals on 4 locations.
115 games, nearly each with different referee. For all matches Squore was used with automatic transferring results to our website.
Overall a big success as all locations gave a positive feedback (on 2 I was personally).

Let me give you some feedback and maybe we can even improve the product and user experience.

I detected 3 problems I want to tell you

1. There were some problems with a hanging app. It occurred on different devices of different manufactures.
   Usually a restart of the app helped. One time the user did a reinstallation of Squore. I know this is a quite fuzzy error description, but I don't know what to tell more.
2. There are still issues with the credentials (see issue saved credentials disappear, when switching the feed #81). They have been "forgot" on some devices. Maybe because the feed was switched from the league to a tournament and back to the league. Afterwards the credentials are gone. The problem now is, that our process relies on the submission of the result, we have devices owned by the clubs and some users which are not too experienced or even have no personal credentials. So when Squore asks for credentials after the match there was confusion for the users and they always needed support. This is something I want to avoid in future. Do you think it's possible to store credentials, even when changing the post URL or even better store credentials per post URL. Means when changing back to DSQV URL (feed) the "old" credentials will be pre filled out again.
   Sounds like a small point, but this is something very important regarding the acceptance of our whole process.
3. On Saturday I had the issue, that matches didn't appear in the list of matches in "select from feed", even if the list was refreshed and they have been actually there. I checked it with my mobile in parallel and the have been listed.
   I solved the issue reducing the property "Feeds: max cache age" to 1. I remembered our longer discussions a few weeks ago. Do you see a chance to improve this behaviour? A normal user will never understand why the matches are not listed, even if they should. And for me it looks like this occurs in relationship with default property value 60.

[obbimi]

1. Indeed to little info to go by... If you know how to reproduce that would be great.
2. Since saved credentials disappear, when switching the feed #81 the credentials should already be stored per URL. I could not reproduce the issue with the latest version. Ofcourse when entered the checkbox 'store password' should be checked... If you have specific steps to reproduce... With Config feed to enable centralised deployment #85 implemented you should also be able to specify savePasswords=true in your json
3. You should be able to solve this once Config feed to enable centralised deployment #85 is implemented. Then you publicly available config should be able to set it the max cache age...