Bug: all version of v2.0 up to 2.0.9 downloaded from app store fail displaying Home, Profile -- but building 2.10 locally works (584089912)

[stepheneb]

Environment:

• OS: iOs 18.7.1
• IceCubesApp version: 2.0.9

Description

This is a strange problem that I expect nobody else has.

I've had a problem will all versions of v2.0.x up to 2.0.9 where trying to display my home timeline displays no posts and reports an error suggesting I retry. Selecting my local timeline (ruby.social) works. Selecting my profile displays a section of rectangular placeholders for text with no text. Tapping on the Settings control displays a menu with similar rectangular containers for menu items with no text.

Before ever installing v2.0 I had been running a version of a late 1.0.x that I had built locally and deployed to my iPhone SE3. I kept running this version while occasionally testing new releases of the 2.0.x series.

I suspect deploying my local build of 1.0.x is related to this issue because I'm sure other folks would have reported this issue already.

Maybe there are some permissions associated with parts of the settings that the deployed from the app store version didn't have access to. I found it quite strange that v2.0.x correctly displayed my local timelines and reported errors elsewhere.

So today my working version of 1.0.x that I built and deployed said it could no longer run (maybe exceeded some time limit for a locally deployed app built for "testing"). I tried to rebuild it but that didn't work because EmojiText reports this error: 'AttributedPartialstring' does not conform to protocol 'AttributedStringProtocol' ...sigh

So I cloned the latest v2.0.x, 5840899, built and deployed it locally and it works fine. Yay.

Once I had everything setup with my credentials, and created an icloud and group in my apple developer account building works fine.

Might get inspired to look at some bugs if they cause problems for me.

PS: Also going through that much work is an interesting indicator of how much I like using IceCubes.

Related Issues

• Search that this bugs don't already exist before creating it.