[Buzzvil] Updates to SDK versioning and EOL policies
Notice: December 5, 2025
Hello from Buzzvil.
We are announcing the end of support for iOS 13 and earlier in BuzzAd SDK for iOS.
End of support for iOS 13
To respond to changes in Apple's policies and improve service quality with newer technologies, BuzzAd SDK for iOS will end support for iOS 13 and earlier on January 1, 2026.
All BuzzAd SDK for iOS versions released from 2026 onward will be optimized for iOS 14 and later. We recommend setting your deployment target to iOS 14 or later for reliable service and access to the latest features.
Required steps
If your app supports iOS 13 or earlier, take the following steps:
- Update the deployment target: Set your Xcode project's deployment target to iOS 14 or later.
- Update the SDK: Upgrade to the latest BuzzAd SDK for iOS for performance improvements and new features.
- Check compatibility: Verify that your app's main features work correctly on iOS 14 and later.
Thank you for your continued support and feedback. We look forward to working with you to build better monetization solutions. If you have questions, contact your Buzzvil representative or help@buzzvil.com.
Thank you.
The Buzzvil team
Notice: March 31, 2025
Hello from Buzzvil.
We are announcing updates to Buzzvil's SDK versioning policy, effective March 31, 2025. From that date, SDK version lifecycles will follow the revised policy. Please read the changes below to understand the updated SDK versioning and EOL policies in advance.
With this policy, Buzzvil aims to improve SDK quality and stability while delivering new monetization features more quickly as Korea's leading ad tech company.
Lifecycle changes for BuzzAd and BuzzScreen SDKs
With the March 2025 release of Buzzvil SDK v6, which combines the strengths of WebView and native implementations to improve monetization and user engagement more quickly, service for Buzzvil Android and iOS SDK 5.x and BuzzScreen SDK 5.x, released from October 2023 onward, will end on December 31, 2025.
SDK products whose availability and technical support were scheduled to extend beyond December 31, 2025 will instead reach both milestones on that date, regardless of release date. See the end-of-support schedule by product and version for details.
All subsequent releases of these SDK versions will also reach end of service on December 31, 2025, regardless of release date. Features that improve business performance will be added to 6.x; 5.x will receive only essential updates, such as platform policy changes. We recommend migrating to the latest Buzzvil SDK 6.x at least three months before December 31, 2025.
Effective date
Effective March 31, 2025.
Thank you for your continued support and feedback. We look forward to working with you to build better monetization solutions. If you have questions, contact your Buzzvil representative or help@buzzvil.com.
Thank you.
The Buzzvil team
Notice: March 7, 2024
Hello from Buzzvil.
We are announcing updates to Buzzvil's SDK versioning policy, effective March 7, 2024. From that date, SDK version lifecycles will follow the revised policy. Please read the changes below to understand the updated SDK versioning and EOL policies in advance.
With this policy, Buzzvil aims to improve SDK quality and stability while delivering new monetization features more quickly as Korea's leading ad tech company.
Lifecycle changes for BuzzAd and BuzzScreen SDKs
Following the October 2023 release of BuzzBenefit (referred to here as Buzzvil SDK 5.x), service for BuzzAd Android and iOS SDK 3.x and BuzzScreen SDK 4.x, released from December 2021 onward, will end on December 31, 2024.
End-of-service dates have been adjusted for BuzzAd Android SDK 3.31.x and later, BuzzScreen Android SDK 4.25.x and later, and BuzzAd iOS SDK 3.25.x and later to provide a total lifecycle of at least one year and six months of maintenance after the March 7 announcement. See the end-of-support schedule by product and version for details.
All subsequent BuzzAd SDK 3.x and BuzzScreen SDK 4.x releases will reach end of service on December 31, 2024, regardless of release date. We recommend migrating to the latest Buzzvil SDK 5.x at least three months beforehand.
Effective date
Effective March 7, 2024.
Thank you for your continued support and feedback. We look forward to working with you to build better monetization solutions. If you have questions, contact your Buzzvil representative or help@buzzvil.com.
Thank you.
The Buzzvil team
Notice: June 1, 2023
Hello from Buzzvil.
We are announcing updates to Buzzvil's SDK versioning policy, effective June 1, 2023. From that date, the scope of SDK technical support will change under the revised policy. Please read the changes below to understand the updated SDK versioning and EOL policies in advance.
With this policy, Buzzvil aims to improve SDK quality and stability while delivering new monetization features more quickly as Korea's leading ad tech company.
Why the policy is changing
Buzzvil SDKs follow semantic versioning, with X.Y.Z defined as 주.부.수. Previously, hotfixes were applied to every minor version still within the 18-month lifecycle defined by the EOL policy. This required managing a large number of versions across all SDK products and the constraints that came with them.
To better support our customers' growth through app monetization, Buzzvil will now manage lifecycles around the most recently released 주 version and focus the scope of new features, improvements and bug fixes.
This approach supports our commitment to high-quality products and operational services. It lets us deliver features and fixes more quickly and efficiently, improving SDK quality and stability for all customers.
Effective date
Effective June 1, 2023.
EOL policy changes
The EOL policy changes the versions covered by lifecycle management and the lifecycle stages.
Versions covered
Lifecycle management is based on the X (주) version in X.Y.Z (주.부.수). Changes are highlighted below.
| Before | After |
|---|---|
| To provide a reliable advertising platform, Buzzvil maintains an EOL policy defining support services and the lifecycle of its SDK solutions. This policy takes effect on December 21, 2020 and applies to all software development kits (SDKs) used to integrate with Buzzvil's advertising platform. It defines the services provided during the product lifecycle. Buzzvil regularly releases new or updated features, improvements, bug fixes and documentation updates. We recommend keeping your SDK up to date for the latest features, security updates and stability improvements. Continued use of unsupported versions is not recommended. You can choose when to update. | To provide a reliable advertising platform, Buzzvil maintains an EOL policy defining support services and the lifecycle of its SDK solutions. This policy takes effect on June 1, 2023 and applies to all software development kits (SDKs) used to integrate with Buzzvil's advertising platform on a major-version basis. It defines the services provided during the product lifecycle. Buzzvil regularly releases new or updated features, improvements, bug fixes and documentation updates. We recommend keeping your SDK up to date for the latest features, security updates and stability improvements. Continued use of unsupported versions is not recommended. You can choose when to update. |
Lifecycle
The scope of SDK support during Maintenance is changing. Changes are highlighted below.
| Before | After |
|---|---|
|
|
SDK versioning policy changes
Buzzvil's SDK versioning policy, which uses X.Y.Z (주.부.수), redefines which versions receive new features, improvements and bug fixes. The changes are listed below.
| Category | Before | After |
|---|---|---|
| New features |
|
|
| Improvements |
|
|
| Bug fixes |
|
|
Our commitment to customers
This policy lets Buzzvil focus resources on the following priorities to deliver more value and respond to customer needs faster.
- Develop features that help customers monetize more quickly and effectively.
- Improve the user experience with engaging, user-centered design.
- Advance the technology to deliver better business results.
Backward compatibility, security, performance, documentation, support and maintenance planning remain top priorities regardless of the versioning changes. Stability was our first consideration in adopting this policy. We will continue to consider backward compatibility to reduce the work involved in minor-version upgrades and communicate clearly about versioning policy and any changes that affect customers.
Frequently asked questions
Q. I changed only the version number to upgrade from an older release to the latest minor version, but the build fails.
A. The build failed because the latest minor version did not preserve backward compatibility with the older version. We will continue to support compatibility as before. Contact Buzzvil to request a compatibility fix. Such fixes are provided only in the latest minor version, so please update to it.
Q. I found a bug in an older version and want to stay on the same minor version.
A. Under the revised policy, the fix will be released in the latest version. The latest version is intended to preserve the behavior of your current version. Please update to it.
Q. If major versions change more often, how frequently will that happen?
A. Under the revised EOL policy, each major SDK version has a lifecycle of up to 18 months. In exceptional cases, changes to underlying libraries may break compatibility and require a major version increase. We will work to minimize the effort needed for major-version migrations.
Thank you for your continued support and feedback. We look forward to working with you to build better monetization solutions. For SDK version questions, contact your Buzzvil BD manager or help@buzzvil.com.
Thank you.
The Buzzvil team