Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

During CI, publish iOS app to TestFlight #387

Closed
bruno-garcia opened this issue Mar 26, 2021 · 4 comments
Closed

During CI, publish iOS app to TestFlight #387

bruno-garcia opened this issue Mar 26, 2021 · 4 comments

Comments

@bruno-garcia
Copy link
Member

This setup exists on sentry-cocoa and is useful to do some "manual testing" before a release without the need to build locally and run on a device.

A failed attempt here: #340

Potential to extra the work done on https://github.com/getsentry/sentry-cocoa into a git repo that can be added via gittree or submodule to be reused/maintained across repos. We'd like to see this in also with other repos such as Unity, Flutter, Cordova, React Native and Xamarin.

@denrase
Copy link
Collaborator

denrase commented Sep 12, 2023

@kahest Someone would need to create the app with bundle id io.sentry.flutter.example and name Sentry Flutter Example on AppStore Connect, as I do not have the permissions to do so.

@denrase denrase mentioned this issue Sep 12, 2023
7 tasks
@denrase
Copy link
Collaborator

denrase commented Oct 24, 2023

@kahest Any update here?

@kahest
Copy link
Member

kahest commented Jan 15, 2024

@denrase created with app id io.sentry.flutter.sample and name Sentry Flutter Sample

@denrase
Copy link
Collaborator

denrase commented Jan 30, 2024

@buenaflor We sill need the PP in the match repo (if it was not added in the meantime), any update?

@denrase denrase mentioned this issue Mar 18, 2024
6 tasks
kanban automation moved this from To do to Done Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants