New iOS and Android Apps - Bug Reports and Suggestions

[Pushka]

Subscribed link can take forever to fire up. Agree with others that it's now difficult to work out what you have and haven't read.

Stupid Q - what's the diff between subscribed and participated ... are they not the same thing?

You subscribe to threads you might not want to post in but refer to. I only have one. It keeps that clean as a quick reference. Participate is obvious. There are obviously stacks of those. Some of them you might want to subscribe to in order to find them quickly.

Seems like emoticons arent working either now.

This used to be a smile. (looks fine on desktop though)
This used to be a big smile ditto
This used to be embarrassed. ditto

Grrr. And why am I getting huge gaps here?


I guess maybe the developers thought the same as you - they are the same. But that isn't how most users use them.

 

[anat0l]

Using the Android app here, and...

• Definitely could use the ability to have more than 10 posts per page.
• After attempting to open the 3rd topic (e.g. browsed the forums, open one topic, back to list, open another (2nd), back to list, open a third...), nothing happens. No timeout indication is given. Sometimes the breadcrumb trail will load, but not the topic and posts. The app isn't frozen; I can go back to the previous list I was viewing, though similar attempts to open another topic also fail.
  Network monitoring with a known good connection shows that when the app is attempting to load a topic "unsuccessfully", there is no transfer (up or down) of data.
  Quitting the app and reloading it again may make opening topics possible again, until the next 3rd topic to be opened fails.
  I am finding the new app really frustrating for this reason.
• When in the content editor (new post, etc.), I can't see the cursor. Stuff appears when I type, but the cursor is invisible.
• A bug shared with the Tapatalk-based app, lists (i.e. using the [noparse]
  • ...
  [/noparse] don't display properly (full BB code for lists is shown instead)

Now I haven't tried techniques like clearing the cache, logging out then logging in again, or deleting the whole app and reinstalling (I have the correct version of app!), but anyway, those are the problems I was having.

I have to admit that I cannot rely on the (if I understand correctly) bespoke AFF app. The Tapatalk version was clunky indeed, but it did work, though I'm not necessarily suggesting a unilateral re-adoption of the Tapatalk app.

 

[Cynicor]

Finding this app really hard to use. I used to just pick up the phone and read something quickly, even if I was using the laptop. I've cut my AFF phone viewing significantly.
At the very least, thread navigation needs to be at the top and the bottom. Mine does something funky if I scroll down too fast to get to thead navigation, and opened threads re-open at a random date in May (13th) for me...

 

[AviationNZ]

Based on all the feedback, I wonder if it's possible to roll-back to the previous version until more development/testing is done?

 

[pjm99au]

Going to try rolling back the app from a backup tonight. Finding the new version very hard yards to use

 

[dairyfloss]

Based on all the feedback, I wonder if it's possible to roll-back to the previous version until more development/testing is done?

I do hope so... and in the interim, until this thing is working, the AFF paid subscription might need to be put on hold. I have my renewal reminder banner up on the desktop version of AFF (which is all I can use with decent functionality since July 2), and that has served to remind me that the mobile app functionality was the main reason I subscribed in the first place..........

I do hope it's fixed soon, either way. Amazing how much you come to rely on such simple things!

Edit: Actually... I'd lose my earlier subscription rate if I hold/cancel, and have to pay 43% more to start over... well played, AFF!

 

[Craigie]

And right now my iPhone app unread function is sending me back to 01/01/15 on large threads or the first post of threads created after that.

 

[somebol]

The unread list keeps refreshing quite frequently, losing track of where I was on the list

This new app has seriously degraded my AFF experience. Now I am considering switching back to browser.

 

[OATEK]

I have found that I am often back to where I last posted, not where I have read to. The Subscribed threads will not update when you pull down from the top. There is a blue line that indicates it might be polling, but nothing changes, eg the read threads remain greyed, and the 'last' post stays the same. But when you go into a thread you find new posts.

 

[Pushka]

The unread list keeps refreshing quite frequently, losing track of where I was on the list

This new app has seriously degraded my AFF experience. Now I am considering switching back to browser.

I'm using the browser on the phone too.

 

[Princess Fiona]

I'm doing the same thing a fair bit.
I must admit when Beta testing the App I skipped back to the Tapatalk app more often than not as it worked far better.

 

[moa999]

Sounds more and more like this version should not have progressed out of beta.

 

[somebol]

Can we please have the old version back until all the issues are fixed

 

[DeKa]

I agree. Please go back to the old app.
It's frustrating the way iOS updates just installed the new version. I admit I could have auto app update switched off but I've never seen an app go backwards before.

I have two pieces of feedback.

1. When typing replies in Tapatalk, the reply box resizes and gets larger as you type. This new app has a 1.5 line high box so you can only see the line you're typing, and a little more.

2. When tapping a link to another forum post, Tapatalk would open the post in Tapatalk.
This app doesn't seem to understand the link is within the forum and loads it in a web browser window.

 

[anat0l]

I must admit when Beta testing the App I skipped back to the Tapatalk app more often than not as it worked far better.

Did you communicate these concerns in the feedback to the developers during beta testing?


The most brutal criticism of an app and its use should be during the designated testing phases, not go-live.


My hat goes off to the developers for putting together something bespoke for AFF, but it seems the problems which are being expressed here are fundamental.

I actually think it would be fascinating to understand the API and back end systems to AFF and how that interfaces with apps like that being developed. I guess it must be a general Tapatalk API (which is why a general Tapatalk app could be adapted for AFF)...


As a bit of an update, I deleted all my cache and settings from the app and started afresh. No difference to the problems I outlined have been seen - I still need to regularly quit and restart the app to make some progress.

 

[travelislife]

Argh! I 'accidentally' updated this app through updating all my apps with one click, should have come here searching and having a read beforehand. So annoying, I am finding the app a PIA to use, has anyone succeeded in rolling back? Same problems as everyone else.

 

[Pushka]

I was hoping that I could manage the app by using the Unread function then selecting the 'tick' to mark all as 'read' when I was done. But that doesnt seem to work either as I still see threads from a couple of hours ago that haven't been updated but still showing as unread. So some basic issues occurring.

 

[RooFlyer]

Still getting about a 50% hit rate with 'Subscribed' resulting in a blank screen when opened. Often get the whole screen flashing in an unstable-looking way, on any of the ... what do you call them ... ?feeds? ('Subscribed', 'Unread', 'timeline' etc). (iPhone 6)

 

[Princess Fiona]

This happens fairly frequently on the Timeline

Double posting of the same threads

 

[Freq Flier 2013]

I've had the double posts as well in my timeline