1728 is the ID of the Event: namespace, which is super suspicious. The page displays normally in the web version, so I assume this is an issue with the android app. I wouldn't be surprised if it happened for all pages in the namespace.

Thanks Daimona.
I don't have time anymore today for testing, but will return to my desktop on Thursday and can see if I can test this further,

Hi @JTannerWMF & @HNordeenWMF!

We're seeing event pages with event registration fail on the Android app (I don't know if this also happens on iOS), though they work on mobile web. I am guessing this is because we do not yet support the CampaignEvents extension in the app.

In the short-term, we probably want some error message that is more descriptive to display in the case shared above. Even better, we could at least display the event page information without the event registration header (which I was able to see for events that are not in the event namespace - for example, this event page looks the following way in the Android app).

In the longer-term, however, the better option is to support the CampaignEvents extension in the apps. I know this is something we have discussed in the past, but it is especially pertinent in this new fiscal year, since we're interested in expanding usage and adoption of the extension tools under WE 1.2. Curious to hear your thoughts!

dbrant opened https://github.com/wikimedia/apps-android-wikipedia/pull/5750

This is because, for extremely legacy reasons, we are using a hardcoded enum with a list of known namespaces. If a new namespace is introduced that doesn't exist in our enum, it will throw an exception.
We could patch this up pretty easily and get it into our next app update (this week). (but a longer-term solution will be to no longer use a hardcoded enum for namespaces.)

Thanks for the explanation and clarification, @Dbrant! This all sounds great to me.

Meanwhile, I can continue the conversation with Haley and/or Jaz about supporting the extension in the apps, but it doesn't need to specifically happen in this ticket. Appreciate it!

cooltey closed https://github.com/wikimedia/apps-android-wikipedia/pull/5750

Testing on 2.7.50539-r-2025-07-08. I think this is fixed but I ran across a couple of issues that I wanted to communicate:

• Opening the event URL from the ticket does not offer the ability to open in App for me. Perhaps that is by design.
• On this page it appears that the user can 'register' for the event, but they cannot access the header where the actual registration button resides. This may be a little confusing and something we should revisit in the future.

We may want to kick people out to mobile web. I am putting this in the backlog until the Connection team's QA engineer fully tests the experience.

Update is that QTE investigation from Connection team on support for the CampaignEvents extension in the apps will be tracked in T400773. It hasn't started yet, but it will begin soon.

This is redirecting me out from the android wikipedia app to a mobile web version of the event, which I believe is the expected behavior now? Once on the web app, I can successfully register (had to pick another event to test this functionality on, the one in the task description is now closed).

Also, I will note that I am unable to search for anything in the Event namespace from the mobile android app, which is why I used Special:AllEvents to find an event to test this on. But that is out of scope for this ticket.

I didn't know how to link to a page inside the app: happy to fix the link in my original post to clarify.

dbrant opened https://github.com/wikimedia/apps-android-wikipedia/pull/5845

cooltey closed https://github.com/wikimedia/apps-android-wikipedia/pull/5845