Skip to content

test: more override config #5201

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

Open
wants to merge 24 commits into
base: armcknight/test/restart-sdk-on-reconfig
Choose a base branch
from

Conversation

armcknight
Copy link
Member

@armcknight armcknight commented May 7, 2025

Adding more config option overrides and reorganizing in the yml spec. This originally started when I was moving the Camera sample app to use the sdk wrapper and shared overrides.

TODO

  • Ensure that any option set in SentrySDKWrapper.swift has a corresponding override in SentrySDKOverrides
  • Gonna leave this for a subsequent PR to keep this one from getting too big: - [ ] Do it again, but for iOS-ObjectiveC, since we need to make sure usage of options from objc compiles, but we don't yet have other objc sample apps, so don't need an objc wrapper just yet

#skip-changelog

Copy link
Contributor

github-actions bot commented May 8, 2025

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 1220.37 ms 1234.89 ms 14.52 ms
Size 23.76 KiB 819.63 KiB 795.87 KiB

Baseline results on branch: armcknight/test/restart-sdk-on-reconfig

Startup times

Revision Plain With Sentry Diff
84083f2 1233.36 ms 1250.71 ms 17.35 ms
bca2ddd 1230.17 ms 1255.33 ms 25.16 ms
5f32b69 1219.33 ms 1245.29 ms 25.97 ms
3e116c4 1218.68 ms 1238.50 ms 19.82 ms
32e3ad8 1228.22 ms 1241.59 ms 13.36 ms
c96b284 1224.82 ms 1249.02 ms 24.20 ms

App size

Revision Plain With Sentry Diff
84083f2 23.76 KiB 819.49 KiB 795.73 KiB
bca2ddd 23.76 KiB 870.65 KiB 846.89 KiB
5f32b69 23.76 KiB 870.58 KiB 846.82 KiB
3e116c4 23.76 KiB 865.92 KiB 842.16 KiB
32e3ad8 23.76 KiB 865.91 KiB 842.15 KiB
c96b284 23.76 KiB 870.58 KiB 846.82 KiB

Previous results on branch: armcknight/test/more-override-config

Startup times

Revision Plain With Sentry Diff
0ff4ed9 1211.19 ms 1240.78 ms 29.59 ms
7694978 1236.12 ms 1240.53 ms 4.41 ms
8eaa1b9 1216.39 ms 1243.00 ms 26.61 ms
a81288b 1235.84 ms 1250.69 ms 14.86 ms

App size

Revision Plain With Sentry Diff
0ff4ed9 23.76 KiB 819.63 KiB 795.87 KiB
7694978 23.76 KiB 870.85 KiB 847.09 KiB
8eaa1b9 23.76 KiB 870.84 KiB 847.08 KiB
a81288b 23.76 KiB 819.62 KiB 795.86 KiB

@armcknight armcknight marked this pull request as draft May 8, 2025 08:18
@armcknight armcknight force-pushed the armcknight/test/more-override-config branch from 02587a2 to 99bb9dd Compare May 13, 2025 08:24
@armcknight armcknight changed the base branch from armcknight/test/restart-sdk-on-reconfig to armcknight/test/sample-app-debug-menu May 13, 2025 08:24
@@ -66,7 +66,7 @@ public class SentryReplayOptions: NSObject, SentryRedactOptions {
/**
* Used by Hybrid SDKs.
*/
static func fromName(_ name: String) -> SentryReplayOptions.SentryReplayQuality {
public static func fromName(_ name: String) -> SentryReplayOptions.SentryReplayQuality {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How bad would this SDK change be @philipphofmann

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it wouldn't be ideal but also not terrible. We could still mark it as "do not use this".

If we just need it internally, we could consider using @_spi(Private) (cc @noahsmartin)

@armcknight armcknight force-pushed the armcknight/test/more-override-config branch from 99bb9dd to 3172bce Compare May 13, 2025 20:52
@armcknight armcknight changed the base branch from armcknight/test/sample-app-debug-menu to armcknight/test/dns-view-in-debug-menu May 13, 2025 20:53
@armcknight armcknight marked this pull request as ready for review May 16, 2025 03:02
Base automatically changed from armcknight/test/dns-view-in-debug-menu to armcknight/test/restart-sdk-on-reconfig May 16, 2025 18:48
itaybre

This comment was marked as resolved.

@@ -66,7 +66,7 @@ public class SentryReplayOptions: NSObject, SentryRedactOptions {
/**
* Used by Hybrid SDKs.
*/
static func fromName(_ name: String) -> SentryReplayOptions.SentryReplayQuality {
public static func fromName(_ name: String) -> SentryReplayOptions.SentryReplayQuality {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it wouldn't be ideal but also not terrible. We could still mark it as "do not use this".

If we just need it internally, we could consider using @_spi(Private) (cc @noahsmartin)

@@ -34,7 +34,7 @@ class MySceneDelegate: NSObject, UIWindowSceneDelegate, ObservableObject {
var initializedSentry = false
func sceneDidBecomeActive(_ scene: UIScene) {
guard !initializedSentry else { return }
SentrySDK.showFeedbackWidget()
SentrySDK.feedback.showWidget()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

h: The widget i not showing up for me, I assume that something with the window levels could be the issue, but not sure.
Screenshot 2025-05-26 at 09 59 33
Screenshot 2025-05-26 at 10 00 18
Screenshot 2025-05-26 at 09 59 58
Screenshot 2025-05-26 at 10 00 48

@@ -33,7 +33,7 @@ class MySceneDelegate: NSObject, UIWindowSceneDelegate, ObservableObject {
var initializedSentry = false
func sceneDidBecomeActive(_ scene: UIScene) {
guard !initializedSentry else { return }
SentrySDK.showFeedbackWidget()
SentrySDK.feedback.showWidget()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

h: Same as above, not visible in UI.

@armcknight
Copy link
Member Author

@philprime It's getting long enough that I can't quite remember why these calls are already in this branch, but I'm pretty sure the reason it's not showing up for SwiftUI is due to this change not having been merged yet: #5223

@philprime
Copy link
Contributor

@armcknight so what would be the best approach to continue? Merging the PR with the known issue and fixing it then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants