Buildbox 2.3.9 #2600 Is Officially Live!

Howdy Boxers!

So after a very long wait we are officially launching our newest Buildbox 2 update. Presenting Buildbox 2.3.9 #2600. You can update to it within the software or use the links below:

WIN: https://downloads.buildbox.com/buildbox/2.3.9/Win/Buildbox_2.3.9-2600.exe

MAC: https://downloads.buildbox.com/buildbox/2.3.9/Mac/Buildbox_2.3.9-2600.dmg

Change log:
Added: in AdMob rewarded video field in settings
Added: handling of embedded frameworks in iOS exports
Added: AdMob rewarded videos
Updated Android libraries
Updated Android Network Libraries
Updated Facebook for iOS
Updated AppLovin for iOS
Updated: AdMob for iOS
Fixed: In-App Purchase on tvOS
Removed: HeyZap Ad Network
Removed RevMob Ad Network
and other fixes and performance optimizations

Enjoy and have a fantastic weekend everyone!

 

other fixes and performance optimizations …. for Android ?

Nice

 

Many of us loved the version of BB2, with this new update, we will be able to update our games.

 

just updated HopBound with this on both iOS and Android and waiting for approval now.

 

update pushed through with no problems on both stores

 

nice

 

Hello @Sean Buildbox @HueTheDev ,

Unfortunately even after trying this many times all the versions that were shared by BB support, the rewarded video ads for admob doesn't works. So we are now completely standing right away in middle with no direction. Have also tried this latest version release but admob ads aren't appearing now. So we are blunt currently

 

Admob rewarded video works without a problem.

 

Thanks for response, can you let know if rewarded video appears for android version? Because we tried for android version and it doesn't appears

 

rewarded video ads work for both ios and android @bmsingha.

ads may not always appear if you haven't released the game yet.

try the admob test ads and you'll see it works great.

i used this version to update hopbound on both stores and it's working for me

 

Thanks for this confirmation. Yes did tried both the alternatives in our case but didn't worked either in our case. Even tried generating new IDs for the same but didn't resolved, not sure y it's happening so exactly

 

Shot you a DM, waiting on your response but we'll help isolate the variable here

 

T

hanks man, highly appreciate your response and coming to rescue. Sending you

 

hi @sean
for more than a year I have been patient so that the bug is fixed. I sent a video that describes the problem: when I click on the "action button" and on "start". the timers are not reset and continue with the previous count

 

Can you DM me this example BBDOC and will have a look? Is this only in preview or on device as well?

 

hi @sean
the bug is on all basic modules, you can test on any module available on bb2
in fact the bug is on the action button itself
here is module on video http://belmirsoftcolor.com/bb/bugBAcount.bbdoc

 

hi @Sean Buildbox i am getting this error on xcode
" Building for iOS Simulator, but the linked and embedded framework 'AOBSessionReporting.framework' was built for iOS."
i just export my project from bb2.3.9(2600) and load it in xcode 11.4 and then i press play button to test in simulator but suddenly error came and it says build failed and produce this error...please give solution for this

 

Buildbox isn’t going to run using Xcode simulators. You have to use a real device.

 

@Codifie in previous version of bb2.3.9 (2571) i have successfully run my xcode project on simulators, did buildbox restrict in new version not to run on simulators?
i have 2 gamess succesfully tested on simulator and uploaded to appstore from bb2.3.9(2571) but i am getting error(AOBSessionReporting.framework' was built for iOS.") in new version of bb2.3.9(2600)

 

So BB3 will not run with Simulators and never has. BB2 did because of differences in the code. It sounds like this may have changed with our most recent update however. @ahsann can you DM me the full xCode screenshot with the error so I can discuss this with the team?

To be clear we do always strongly recommend testing with an actual device rather than simulators in conjunction with Buildbox however.