PR: https://github.com/wikimedia/apps-android-wikipedia/pull/5017

In T339295#10212831, @ABorbaWMF wrote:

This is not working for me on Pixel 6, Android 14. Testing on 2.7.50505-r-2024-10-07

T374058 has been merged, so this should be good to proceed.

@Tsevener This is now merged and deployed!
Each of the schemas mentioned in the task description gets a version bump of +1 in the minor version.
The is_temp field is technically optional (necessary for backwards compatibility), but can now be sent to any of the above schemas.

In T376502#10203797, @Kemsguy wrote:

@ARamadan-WMF , would love to work on this issue, would you mind assigning it to me?

Verified in collaboration with fr-tech; see Slack thread. (Made a test donation, and verified in the backend that the banner parameter was correct.)

Not sure this merits another full-blown regression test. The specific changes that were cherry-picked will be tested via the individual tickets currently in QA.

For QA:

• In the latest Beta, make a test donation, or alternatively click this link to simulate completing a donation.
  • Tapping the above link (from your phone's browser) should land you in the app, showing the "thank you" page.
• Go to Developer Settings, and nearly all the way at the bottom (third from bottom), you should see an item called "Donation results", which should contain some text that states the date of the completed donation.

There turned out to be a sneaky issue where, due to a quirk of the Kotlin language, the campaign ID was being overwritten and reverted to the default appmenu id.
This has now been resolved.

Sorry, this has already been done. (this issue seems to have been missed from the pull request that resolved it.)

Our Play Store listing verbiage was quite out-of-date: it was still mentioning our collecting crash reports through Microsoft AppCenter, which we haven't used in years.
I have removed the references to AppCenter from the description, and the reference to the option of "disabling" these crash reports, which no longer exists.

@SNowick_WMF Note that android_article_page_scroll_interaction and android_reading_list_interaction do not seem to be used in the app.

APK:
https://github.com/wikimedia/apps-android-wikipedia/actions/runs/10850026211

In T370316#10142356, @Prototyperspective wrote:

Would a screenshot be helpful or are things clear enough and this problem easily reproducible on test devices? (again, third grey from left in color scheme then scroll to bottom of any article)

yes it can!

The big overarching limitation for this effort will be that we need to store all of this information locally (not just locally, but local to the current install of the app), i.e. with no syncing of this information to the backend, and no additional infrastructure planned.
This has the following implications (not limited to):

• The app cannot know whether the user has made donations in the past, or what amounts they were.
• If the user signs up for a recurring donation through the app, and then later cancels it (which is done outside of the app), the app won't be able to know about it.
• If the user uninstalls and reinstalls the app, or clears the app's data, their local contribution history will be lost.
• If the user logs in on another device, their contribution history will be empty.

Should already be resolved a while ago. Please reopen if this is still an issue.

(latest apk: https://github.com/wikimedia/apps-android-wikipedia/actions/runs/10778565666)

(latest apk: https://github.com/wikimedia/apps-android-wikipedia/actions/runs/10778565666)

(latest apk: https://github.com/wikimedia/apps-android-wikipedia/actions/runs/10778565666)

In T338266#10127272, @cmadeo wrote:

@Dbrant I'm still seeing 'anon' edits and the person / anon icon rather than the temp account icon:
(on Test wiki with last two edits made by me with a temp account)

Seems like a PCS issue, where certain hatnotes get placed below the lead paragraph: