Nate Macleitch

Shared instance QuickBlox application upgrade on 3rd March at 15:00 EET

Posted by Nate Macleitch on March 3, 2017

QuickBlox Shared instance account owners,


Please be informed that backend upgrade scheduled on 2nd March has been postponed and is going to be performed today on 3rd March 2017 at 15:00 EET.


The upgrade has been postponed due to the delay in migration scripts performance.

We are very sorry for this inconvenience.  


During the maintenance you may notice about 10 minutes downtime and short interruptions.
Thank you in advance for understanding and patience.

Nate Macleitch

Shared instance QuickBlox application upgrade on 2nd March 15:00 EET

Posted by Nate Macleitch on March 1, 2017

QuickBlox Shared instance account owners,

Please be notified that backend upgrade, that was scheduled on 1st March is postponed on tomorrow – 2nd March due to issues with AWS services on 28th February.


On the 28th of February 2017 at approximately 17:40:53 GMT+0000 (UTC) our engineers were alerted to AWS experiencing increased error rates for Amazon S3 requests in the US-EAST-1 region.


You can find more details on the status post here:

During this time, AWS customers with S3 bucket located in US East Region experienced issues with adding new objects into S3 bucket.  

Nate Macleitch

Maintenance on Shared instance on March 1st 15:00 EET (Wednesday)

Posted by Nate Macleitch on February 24, 2017

Please be notified that we are releasing a major architecture change on the Shared instance (

This changes can affect YOUR application so please review the information below.

We will upgrade the QuickBlox Shared Instance to a new backend architecture on March 1st, 2017.

We are making these changes to improve system performance and efficiency.

This architecture has already been deployed on our Enterprise Customer Servers resulting better performance for these customers.

With this new architecture release the QB team will be able to more easily implement additional performance improvements and as a result provide you with better service.
Previously a QuickBlox account owner could have multiple users registered with the same email address across several applications within one QuickBlox Admin account


This approach to USERS created performance issues. This is why we removed the ability to create USERS with the same email over 1 year back.

In the new architecture of the Quickblox Shared Instance each USER email address MUST be unique within one QuickBlox application ADMIN account.

This means that one user will be able to login to only *one* application with one and the same email address.




We ask customers who have users shared across more than one application to either:

  1. Prioritize their applications and make sure that before the 1st of March system change assign USERS to the application where they should be.

The detailed instructions about necessary changes were provided via admin panel and emailed previously to customers.

In case you do Nothing before March the 1st, 2017, during the upgrade users will be assigned to the applications which they accessed most often based on the number of sessions created for those users in the applications automatically.

  1. Create additional ADMIN accounts for each application

You can continue to have multiple applications and the same registered USERS across multiple applications – However these users must be separated in different account.

As an alternative solution you can contact QuickBlox sales team ( ) to request migration of your application on dedicated Enterprise instance with current backend software version.

Nate Macleitch

iOS Video calling(WebRTC) SDK with dynamic framework, reduced size and Bitcode supported

Posted by Nate Macleitch on January 27, 2017

Today we’re proud to announce the new version iOS video calling (WebRTC) SDK 2.4 with 3 new killer things:

  • Bitcode supported. Apple added Bitcode binary support for developer apps as part of the app thinning process. The main reason behind this is to minimize the end user download app size.
  • Built as dynamic framework.  To develop apps, programmers link their custom code against these libraries to get basic functionality. However, linking to libraries creates large executable files and wastes memory. One way to reduce the file size and memory footprint of apps is to reduce the amount of code that is loaded at app launch. Dynamic libraries address this need; they can be loaded either at app launch time or at runtime. Dynamic libraries provide a way for apps to load code when it’s actually needed
  • Reduced size of our framework from 84.3 mb to 67.4 mb. Bitcode support and dynamic framework itself have allowed us to reduce our framework size in ~21%.

We want to provide you an ability to give your users the best user experience you can. And these 3 features are directly connected to it.

Read full QuickbloxWebRTC SDK 2.4 changelog.

Have a great time using the SDK!