maybe we could use comm's system

did a little brainstorming in planning, we might need a separate system for translating short-lived strings in a smaller time window

Resolving, will reopen if the crash appears again in HockeyApp

I can see the code that changed it, unfortunately I'm not seeing a large difference in memory usage. NSCache (infamously) omits any guarantee that it will evict objects once the count limit is exceeded. And after browsing many POTD and several articles, I should have easily hit 50 images and started to see things level off. Resolving that the work was done, but it's unclear if there was any significant improvement.

@JMinor need access to Google doc w/ screenshots

some formatting tweaks and updated the "Feedback" instructions. Also, our "feedback" mechanism is really, really buried. At the very least we should make it a button in Settings (instead of a link at the bottom of the "About" page).

More like a performance enhancement

so in the app store, the app would just pick one

@JMinor @Josve05a this isn't a crash, it's an assertion since normally (when there's only one image "displayed"), we only expect to get one visible image. however, in this case we could just pick the left-most (or right-most in RTL?) or disable chrome interaction entirely while scrolling

Also, strangely fitting how that title stays at the top of the list... Damn robots

Aww I actually clicked on that one :-(

here's the group across multiple versions: https://rink.hockeyapp.net/manage/apps/152725/crash_reasons/112245983/multiple

probably this one: https://rink.hockeyapp.net/manage/apps/152725/app_versions/161/crash_reasons/112245983

turn off network connection

So you can experiment w/o changing code? Just a suggestion.

@JMinor flagged this as high prio to fix before release if possible. please adjust if necessary

@Nirzar yeah, would be trivial to add one.

@Nirzar k, tweaking the timing is 1 sec (and adding a tweak for the duration is another second), but please check w/ @JMinor before putting in add'l work on this. There are lots of other outstanding crashes that should be worked on before release.

@Nirzar @Mhurd looks good! However, I think the animations are too slow. 1.3 seconds is a long time (over 5x the default animation duration of 250ms) to have to wait to see & interact w/ content. This is especially dangerous in the FTUE, as I worry we could potentially hinder our first impression by frustrating w/ views with an artificially slow experience. We need to strike a balance between visual embellishment and efficiency.

i.e. those are the actual "LICENSE" files for the repo

@JMinor correct, it's all from GitHub as extracted by CocoaPods

oh you mean for the app's license? we can link to the file on GH if that's sufficient

@ZhouZ @Josve05a the licenses are now all available in their entirety in a separate menu if you tap on the Licenses link:

One more thing, just exported an IPA specifically for my iPhone 6, and it weighs in at a whopping 7MB. It even comes with a nifty "App Thinning Size Report":

So, this is a ubiquitous issue w/ these chevrons outside of a navigation bar. For example, also happens in "More" menus in Explore sections (e.g. More nearby, More recommendations for an article, More most read).

Technically this could happen for any project, but only current seems to happen for HE wiki. Ideally we would fetch these in batches, but the safest (and simplest) thing to do is to fetch previews for titles individually.

Also, I think I fixed this as part of my work on T127893 (PR #512)

@Fjalapeno that's the task ID of this ticket, did you mean another one?

for posterity, he meant POTD, not Pod

going to resolve this with the Pod and the nearby ticket

Moving back to "blocked" so one of us can add RTL compliance for this button

I merged this already, but just discovered it doesn't work in RTL:

@Moushira in-app bug reporting implementation difficulty is most a product of the reporting tool itself. Specifically, its API usability, but pre-existing client SDKs are also immensely helpful. I'm only saying that whatever reporting solution we chose should highly prioritize making the feedback flows as seamless as possible, trying to keep people in the app.

It seems to only happen when the random card is at the top of the screen.