We are using SDK version 5.7.6 and we are joining meetings and starting ad-hov meetings using userid password.
We noticed that your removed support for this in Windows Meeting SDK v5.9.0.
tual SDKError IsEmailLoginEnabled(bool& bEnabled) = 0;
virtual SDKError Login(LoginParam& param) = 0;
This change was made with no announcement and we are unable to get any support from your staff as with any problem we get the trite message “update to the latest SDK”.
Please restore this feature as soon as possible, and please use proper notification to ensure your development community has adequate time to respond to your breaking changes.
Moving forward, you will need to utilize OAuth for user authentication. We will not be adding the email/pw login in any future releases. All accounts with an SDK app were notified of this change multiple times over the last several months, and we will be sending out another reminder in the near future recommending all SDK apps to migrate to OAuth.
When did you send the notification of this breaking change?
'How are we suppose to subscribe to these notifications no one here got any notice.
This change was noted in our release notes, which are posted in the changelog. We also post SDK release notifications in the #announcements:new-releases category.
putting out release notes AFTER you made the change is hardly advanced notice of a major breaking change. Especially when your support staff will only support us when we are on the latest release.
Obviously your development staff knows when they will be introducing a breaking change - can they at least give use 3 months advanced notice prior to making the change? This will allow us to keep our software up to date without causing major production service disruptions to our zoom customers.
You also said that “All accounts with an SDK app were notified of this change multiple times over the last several months” - we never received anything - can you tell us where to subscribe to get these notices?
All accounts with SDK credentials were sent this notice more than 3 months ago. Please ensure that you are monitoring the email associated with your SDK credentials to stay up-to-date with these communications.
There are a few of MAJOR problems here:
(1) You made a BREAKING change to the SDK 3 months ago - with NO prior notice.
(2) Your support team will not give any support unless on the latest version. This essentially forces your SDK users into a corner.
(3) Your notification system does not work. My email is associated with the SDK credentials and I am receive NO notifications of your changes. Nothing in trash, or spam.
You need to escalate these problems to your management. If you are not willing to maintain older releases of SDKs, you MUST give 3 months notice of breaking changes BEFORE you publish.
This is Software Configuration Management 101. Releasing breaking changes then forcing everyone to update to receive support is an extremely poor software management process.
- Sorry, but this is not accurate. We did provide advance notice of this change last year, and sent a few follow-up notices. As mentioned previously, these are sent to all developer accounts with SDK credentials.
- We do our best to support developers using versions that are not the latest release, but it is not always possible. For example, we can help with advising on incorrect usages of the SDK if you’re on v5.9.0, but we cannot release a bug fix specific to that version since that would not be sustainable in the long term. For that reason, any issues which require an update to the SDK to resolve will at some point require an SDK update.
- This is certainly not the experience we want. We can look into why you weren’t being included on these messages in the past. Is your developer account the same one that is being used to login on the dev forum?
Releasing breaking changes then forcing everyone to update to receive support is an extremely poor software management process.
We completely understand that this is not an ideal process for developers. However, there are some limitations imposed on the SDK platform by the Zoom platform itself which may occasionally result in forced updates in order to ensure the best possible experience for all Zoom users. We do our best to provide notice as far in advance as possible, but we are completely open to hearing any feedback on how we can improve this moving forward.
Please re-read your postings. You said you gave notice 3 months ago (the same time you released the change), and now you say you gave notice last year.
So far, you support team has given NO support to us for any SDK other than the current one.
Also, as I have pointed out: Your notification system does not work. My email is associated with the SDK credentials and I am receive NO notifications of your changes. Nothing in trash, or spam. PLEASE fix this.
I highly urge you to take this to your management and improve your development and release practises. If you are going to implement a breaking change you must be able to assist your customers in the transition, and not leave us out in the cold.
As mentioned in my previous reply, we can look into why you aren’t receiving these updates on your developer account’s email. In order to investigate this, can you please confirm whether the account you use on the dev forum is the same one associated with your SDK credentials?