-
-
Notifications
You must be signed in to change notification settings - Fork 226
Bump to cocoa sdk v8.46.0 #4103
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
Conversation
aritchie
left a comment
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 deeper we go with this, the more it seems we should consider a slim binding in the near future
Possibly yes. If we had slim bindings, I wouldn't have had to add all these methods to satisfy the "missing class" errors for classes referred to by the new objective sharpie code. On the other hand, once we have slim bindings, we don't have any easy mechanism to keep these up to date if/when the CocoaSDK API's change... or I guess we would - that would be our unit tests. So we're really need to make sure we had good coverage in our device/integration tests for all the bindings code in that case. |
This reverts commit 690a169
Bumps the Cocoa SDK to version 8.46, which is the oldest version which would be stable for implementing Session Replay (needed to implement #2136).
I also tidied up the
scripts/generate-cocoa-bindings.ps1script a bit. It was starting to get quite large, mostly because we were using it to add lots of API contracts from theSentry-Swift.hfile (rather than tweak contracts generated by objective sharpie). There didn't seem much point in using PowerShell to write static C# code so I moved that stuff out to the following files (where we at least get syntax checking and analysers from the IDE):src/Sentry.Bindings.Cocoa/SwiftApiDefinitions.cssrc/Sentry.Bindings.Cocoa/SwiftStructsAndEnums.csThis hopefully makes the cocoa bindings script a bit easier to read and maintain.