let's work on iOS for some time?

[tomholub]

@sosnovsky @ioanmo226 I've set up milestone https://github.com/FlowCrypt/flowcrypt-ios/milestone/48 to have some useful features in it for iOS.

I would in particular like Ioan to first do FlowCrypt/flowcrypt-browser#5215 on browser extension before moving to iOS.

Ideally also the other 3 assigned issues, but not 100% required.

Was there something else one of you wanted to do on browser extension, before Ioan makes the switch?

I'm imagining, Ioan could be focusing on iOS for 2-3 upcoming months if that's ok.

[tomholub]

Also, our TestFlight build is expired, which is quite annoying for users who may have used it. What should we do? If we go through dry spells like this in the future, should we just not have a TestFlight public build? Or should we be making builds every 60 days regardless?

[ioanmo226]

Nothing for my side.

Was there something else one of you wanted to do on browser extension, before Ioan makes the switch?

Not sure there is good way but AFAIK apple recommends to update app regularly during beta testing period

Also, our TestFlight build is expired, which is quite annoying for users who may have used it.

[sosnovsky]

Was there something else one of you wanted to do on browser extension, before Ioan makes the switch?

No, these tasks should be enough before switching to iOS, also FlowCrypt/flowcrypt-browser#5185 doesn't need any work for now - probably this issue was caused by broken signature file, still waiting for customer's response.

I'm imagining, Ioan could be focusing on iOS for 2-3 upcoming months if that's ok.

Yeah, that's ok, as currently there are no urgent tasks for browser extension, while iOS has useful functionality which needs to be implemented.

Also, our TestFlight build is expired, which is quite annoying for users who may have used it. What should we do? If we go through dry spells like this in the future, should we just not have a TestFlight public build? Or should we be making builds every 60 days regardless?

I think it's useful to have public build, as we have many users of it and can detect possible issues before releasing to App Store. Previous build expired a month ago, so I think for now there is no reason to re-upload the same build with increased build number, let's upload a new build when some new functionality will be implemented. And then we should monitor that new build is uploaded before previous one is expired (every 90 days)

[tomholub]

Hmm, but if we are going to still maintain the TestFlight, then imo we should do a build with increased number (but not increased version) now. It would take yet another month before we can add useful functionality.

[sosnovsky]

Hmm, but if we are going to still maintain the TestFlight, then imo we should do a build with increased number (but not increased version) now. It would take yet another month before we can add useful functionality.

My point was that as our last build expired a month ago then probably all test users switched to version from App Store, and currently there is no need to upload the same build to Testflight.
When new functionality will be ready, we'll upload new build and can add some information that next builds will be released more often, as we had a little break for iOS development.

[tomholub]

@martgil did anyone complain about this on support?

[martgil]

We haven't received any complaints about our TestFlight public build being unavailable. However, some users may have opted for the App Store version of our FlowCrypt app.