Skip to main content
JarSyr
Known Participant
November 1, 2016
Question

Air 24 Beta crashing in iOS

  • November 1, 2016
  • 25 replies
  • 9849 views

My Starling application crashes in iOS device (version 9.3.1) with error

exception, information=ArgumentError: Error #3672: Buffer creation failed. Internal error.

I also tested a blank Starling project with a single Quad on stage. That did not produce the error, but the quad only quickly shows and then the screen goes black.

My application and the blank test project both work perfectly in Emulator.

My app and test project work as expected in the test device when using Air 23.

This topic has been closed for replies.

25 replies

Inspiring
November 25, 2016

Not working for me too on older iOS devices (< iPhone 5s). Also getting the ArgumentError: Error #3672: Buffer creation failed. Internal error.

Participating Frequently
November 24, 2016

We are still experiencing this problem on low-end iOS devices. (iphone 4s, iPhone 5) as of the November 23rd release. Recompiling with AIR 23 works fine.

Participating Frequently
November 24, 2016

Here's the crash report we're receiving.

OS version: iPhone OS 9.3.2

Device Name: iPhone 4,1

ArgumentError: Error #3672: Buffer creation failed. Internal error.

starling.rendering::VertexData.createVertexBuffer():-1

starling.rendering::Effect.uploadVertexData():-1

starling.display::MeshBatch.syncVertexBuffer():-1

starling.display::MeshBatch.render():-1

starling.rendering::Painter.drawBatch():-1

BatchProcessor.finishBatch():-1

starling.rendering::Painter.finishMeshBatch():-1

starling.rendering::Painter.drawMask():-1

starling.display::DisplayObjectContainer.render():-1

starling.display::DisplayObjectContainer.render():-1

starling.display::DisplayObjectContainer.render():-1

feathers.controls::LayoutGroup.render():-1

starling.display::DisplayObjectContainer.render():-1

starling.display::DisplayObjectContainer.render():-1

feathers.controls::LayoutGroup.render():-1

starling.display::DisplayObjectContainer.render():-1

starling.display::DisplayObjectContainer.render():-1

starling.core::Starling.render():-1

starling.core::Starling.nextFrame():-1

starling.core::Starling.onEnterFrame():-1

deesharm
Adobe Employee
Adobe Employee
November 25, 2016

Hi Darren,

Thanks for your reply.

It will be very helpful for us if you can share a sample project for further investigation.

Thanks,

Adobe AIR Team

Known Participant
November 24, 2016

I'm having issues packaging with AIR 24, but they somehow seem to have to do with Feathers...

AIR 24 packaging issue · Issue #1500 · BowlerHatLLC/feathers · GitHub

fengy12353241
Known Participant
November 24, 2016

I tried the latest AIR 24 Beta SDK. We test on my iphone5c and ipad4, my app did  not have black screen situation. But when I click the login button, or drag the text content, my app crashed and back to desktop.

This is the crash log in ipad:

Nov 24 11:39:35 kaixinde-iPad My App[6814] <Error>: Could not successfully update network info during initialization.

Nov 24 11:39:35 kaixinde-iPad My App[6814] <Warning>: registerForRemoteNotificationTypes: is not supported in iOS 8.0 and later.

Nov 24 11:39:36 kaixinde-iPad My App[6814] <Warning>: getProducts Called..

Nov 24 11:39:36 kaixinde-iPad assistivetouchd[356] <Warning>: Received memory warning.

Nov 24 11:39:36 kaixinde-iPad nsurlstoraged[272] <Error>: realpath() returned NULL for /var/root/Library/Caches/IAPCrazyDemond

Nov 24 11:39:36 kaixinde-iPad nsurlstoraged[272] <Error>: The read-connection to the DB=/var/root/Library/Caches/IAPCrazyDemond/Cache.db is NOT valid.  Unable to determine schema version.

Nov 24 11:39:36 kaixinde-iPad nsurlstoraged[272] <Error>: realpath() returned NULL for /var/root/Library/Caches/IAPCrazyDemond

Nov 24 11:39:36 kaixinde-iPad nsurlstoraged[272] <Error>: realpath() returned NULL for /var/root/Library/Caches/IAPCrazyDemond

Nov 24 11:39:36 kaixinde-iPad nsurlstoraged[272] <Error>: ERROR: unable to determine file-system usage for FS-backed cache at /var/root/Library/Caches/IAPCrazyDemond/fsCachedData. Errno=13

Nov 24 11:39:36 kaixinde-iPad discoveryd[77] <Notice>: Basic DeviceInformation Memory Pressure Warning sent: pressure

Nov 24 11:39:37 kaixinde-iPad SpringBoard[42] <Warning>: Application 'UIKitApplication:com.xxxxxxxxxxxxx[0x7678]' was killed by jetsam.

deesharm
Adobe Employee
Adobe Employee
November 24, 2016

Hi Feng,

Could you please share a sample application with us. It will be very helpful for further investigation.

Thanks,

Adobe AIR Team

deesharm
Adobe Employee
Adobe Employee
November 23, 2016

Hi,

The issue has been fixed in latest AIR 24 Beta Build. Please try testing the same using latest AIR 24 Beta.

You can download AIR 24 Beta Build from here:

Download Adobe AIR 24 Beta - Adobe Labs

Release Notes:

http://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air24_flashplayer24_release notes.pdf

Thanks,

Adobe AIR Team

fengy12353241
Known Participant
November 22, 2016

Hi, dear developers,

We are waiting for the new updating of AIR SDK 24 to deal with the problem.

Thanks.

fengy12353241
Known Participant
November 22, 2016

Hi, dear developers,

We are waiting for the new updating of AIR SDK 24 to deal with the problem.

Thanks.

fengy12353241
Known Participant
November 14, 2016

I also tried AIR SDK 24.0.0.162.

My iphone5c and ipad2 still show black screen, but have not got the error in flash builder and the background music is still playing. It meens only can not show but others are well.

And it has relationship with the device, iphone6/6s/7 are showing well.

deesharm
Adobe Employee
Adobe Employee
November 15, 2016

Hi,

Thanks for sharing the information.

We are investigating it further at our end.

Thanks,

Adobe AIR Team

fengy12353241
Known Participant
November 14, 2016

When I use the Beta SDK 24.0.0.153 to build my app and run it in my iphone5C, it is crashing and showing black screen. It seems the same problem to others. But my app in the iphone6/6S/7 is well.

And when I used SDK 23 to build my app, it is all right in my iphone5c and other iphones.

i_diev
Participant
November 10, 2016

Hello. I have the same bug with latest beta SDK.