testflight | Scripts for building , packaging , tagging , logging | iOS library

Yesterday I submitted a new version of my app to the app store connect. Even thought it shows a success I can't see my build versions. I have not received an email of whether they received the build or even if it has some errors. Also , I can't see their status in test flight. Is this normal because previously i did not have this problem

testflight showing older versions

After I submit binary processing appears then like the following pic

then after I refresh the page the build never shows

I am working with a team on a mobile application. Everyone would like to use and have this app on their phones. However when I tried to install this app on phones with Xcode I've reached the limit of 5 devices. I wanted to buy an Apple Developer Program account so that I can send this app to other with the help of TestFlight app. Can someone confirm if I understood the information that I found on Apple website correctly:

• I can add testers to the app using the link which will be send to them
• They will be able to download and test the app for 90 days
• They don't have to have Apple Developer Account? (I am not sure about that)
• Since the app will not be published but only uploaded for testing it will not have to go through review process

If someone has better idea how to install application on around 10 devices I will be happy to hear that. If someone has any experience with uploading Flutter app to iOS I will also be happy to hear if there are maybe some tricky parts during this process.

I have a SwiftUI app with a widget. When I run the app via Xcode (either straight to my device or on the simulator), the widget works exactly as expected.

However, when I run the app through TestFlight, the widget does appear, but it does not show any data -- it's just the empty placeholder. The widget is supposed to show an image and some text, but it shows neither.

I've seen some posts on Apple Developer forums about similar problems. One accepted answer says the following:

1. Make sure that you use Xcode 12 beta 4 and iOS 14 beta 4 on your devices. Make sure that you have placeholder(in:) implemented. Make sure that you don't have placeholder(with:) because that's what the previous beta of Xcode was suggesting with autocompletion and without that you won't get your placeholder working. I think this whole problem is caused by the WidgetKit methods getting renamed but that's another story.
2. As per the release notes, you need to set "Dead Code Stripping" to NO in your extension target's build settings. This is only necessary for the extension's target.
3. When uploading your archive to the App Store Connect, uncheck "Include bitcode for iOS content".
4. Delete your old build from a device when installing a new beta.

I've implemented these suggestions, to no avail.

Here's my code for the widget. It first fetches game data via CloudKit, then creates a timeline:

When I compile my project in Github Actions(bundle exec fastlane beta),shows this error:

I am having absolutely no luck getting push notifications to work in iOS in a Xamarin Forms project.

In AppDelegate.cs, I am calling the following in the FinishedLaunching override:

When I Archive and upload to app store connect to test in TestFlight. It cannot download app and show

Cloud not install [App] The requested app is not available or doesn't exist.

and When I look at previous Builds. It show same message in all build version.

It happen after renew apple development programs.

What happens to a TestFlight app after 90 days if there are no builds (since a build would reset the clock). Would the app in TestFlight simply not be downloadable and/or would the app running on the iOS device also expire (no longer be usable) after 90 days?

My goal is the have the app available beyond 90 days without the user needing to download the a new build from TestFlight.

so my goal is to have the apple pay button show up on devices that support apple pay and be hidden on devices that do not support it.

Currently I have a vc with two buttons, one is an Apple Pay button and one is a button that segues to a normal checkout. I use logic to determine the right buttons to show, if the device supports Apple Pay it'll show both, if not, it'll show the normal checkout button.

Here is an example of the simulator, a device that supports Apple Pay:

This is what it should look like for a device that supports Apple Pay. Here is the logic I use to determine what buttons to show:

So my goal is to have congruent functionality both on the iOS simulator in Xcode and as well as a physical device on TestFlight. So currently, I have a function that handles refunds in my app. On the simulator the function runs perfectly fine in the order I expect it to, but the print statements execute in the wrong order which I'm assuming is the reason for misbehaviour on TestFlight simulations.

Here is the method: