Closed VadymSV closed 6 years ago
Hi @VadymSV,
Thanks for filing this issue! Unfortunately it is prohibitively high overhead for us to release a Xamarin wrapper for each iOS and Android release due to the highly intensive and manual nature of creating the Xamarin wrapper.
We make it a priority to release Xamarin wrappers after critical bugfixes and feature releases to maximize feature availability and stability for our Xamarin users. Our next Xamarin update is planned for Q4.
Regarding iOS 7, what is your timeline for dropping iOS 7 support? Is there a specific SDK version you would need to integrate before that time?
Thanks, Jared
Hi @Bucimis,
You release Xamarin binding one or two times per year - it very bad situation for those who are using them. Such big company as your must do it frequently.
As I mentioned in previous comment you have a critical bug in IOS SDK version 2.24.2 and it was a part of Xamarin bindigs version 1.3. Since than you release version 1.4 after half a year and customers lived with a critical bug for a long time. Consider to manage such situations quick and with higher priority.
For me it would be great to have binding with fix for 2.24.2 issue and with iOS 7 support (at least version 2.24.3).
Thanks, Vadym
Hi @VadymSV,
We just released version 1.5.1 which binds our latest Android and iOS SDKs. We've greatly simplified our release procedure (mainly through introducing Nuget) and our internal processes around release that should allow us to release more often.
I'm going to close this for now. Feel free to open if 1) our release cadence continues to be unsatisfactory 2) you need a new Android or iOS feature/fix binded with high priority.
Thanks, Braze SDK Engineering
Hi. I've faced an issue that most of the SDK versions doesn't have Xamarin binding. For example you have critical bug on iOS that was fixed in version 2.24.2, but you don't have binding for that version. The next after that is version 2.29.0 which doesn't support iOS 7 and I can't integrate it.