-
-
Notifications
You must be signed in to change notification settings - Fork 223
chore(deps): update Cocoa SDK to v8.56.0 #4528
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
690532d
chore: update modules/sentry-cocoa.properties to 8.56.0
web-flow 0847a67
Add SentryViewScreenshotOptions
jpnurmi ac37eb7
Add SentrySession
jpnurmi b906449
Add missing SentrySpan.Serialize()
jpnurmi 325784e
CS0108
jpnurmi e7b1919
Clean up unnecessary modifications for CS0108 (disabled)
jpnurmi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
version = 8.55.1 | ||
version = 8.56.0 | ||
repo = https://github.com/getsentry/sentry-cocoa |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question
new
/CS0108
Why can't (or shouldn't) use
new
here (and inApiDefinitions.cs
),and rather suppress the diagnostic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And should we, consequently, also remove the other usages of
new
?sentry-dotnet/src/Sentry.Bindings.Cocoa/SwiftApiDefinitions.cs
Line 334 in 462d111
sentry-dotnet/src/Sentry.Bindings.Cocoa/ApiDefinitions.cs
Line 228 in 462d111
sentry-dotnet/src/Sentry.Bindings.Cocoa/ApiDefinitions.cs
Line 1867 in 462d111
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem was that the error came from
SentrySpan.g.cs
, not fromApiDefinitions.cs
:https://github.com/getsentry/sentry-dotnet/actions/runs/17763516547/job/50481482686?pr=4528
Is there any other way to get around this? If not, we could indeed remove the respective modifications in
ApiDefinitions.cs
.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to elaborate a bit, I had tried changing the regexp to make
ApiDefinitions.cs
look like this:Still,
SentrySpan.g.cs
generated on the fly looks like this:Which then results in CS0108 :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cleaned up the unnecessary modifications now that CS0108 is disabled: e7b1919
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see ... thanks for elaborating.
Now I'm wondering, does
new
actually have an effect in metadata ... so I'm wondering of removing existingnew
s could be a breaking change 🤔 ... so I'm wondering if we should leave it as it was before my "complaint"UPDATE 1: no ...
new
does not seem to be reflected in ILUPDATE 2: oops ... didn't see your latest comment ... I have no more concerns 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe safer to leave the existing ones intact, after all?