Skip to main content
Known Participant
July 30, 2013
Question

URGENT - released product crippled by RTMFP failure!

  • July 30, 2013
  • 9 replies
  • 2211 views

Hi,

Yup I am duplicating a thread, but I feel this needs pulling into the splotlight, as the other thread was going nowhere.

I have released a product to market, that was working fine with air 3.2 compiled apps and Flash player. Then I had to do an app update and because of the Apple req for the iPhone 5 I had to use air 3.7

This totally killed any compatibility with the existing 3.2 apps and the update. Even worse it has killed the communication that was working fine between air 3.2 and FP!

I have had to release captive air and new iOS apps which gets round the isse for device to device rtmft over local WiFi.

However a big feature of allowing users to control their device via a web browser is gone!

To test, grab the Yo!Bot app from iTunes or Google Play.

Then visit: http://www.yobot.mobi/webdriver.html

They don't talk to each other for me, or anyone else testing.

I have waited patiently for what I presume is a big bug to be fixed since May. Timescales have now got this product to market and I am left with a big hole in the features!

I normally am a huge fan of Adobe and another of my products http://www.arcadie-arcade.com use Adobe air to provision the games.

Who do I have to go an moan at about this not working, the air team or the FP team?

Apologies if I have missed some new config or feature that I need to add, but simply trying the same code base with 3.2 and everything works!

There is a bug in bugbase, but it has stalled!

See the old stalled thread and bug here http://forums.adobe.com/message/5547333#5547333

Help!

Thanks.

This topic has been closed for replies.

9 replies

Adobe Employee
July 31, 2013

Hi,

It's been very unfortunate you are still getting this problem. Now, as per my understanding these were the following status with AIR SDK 3.7:

1 Device to Device = Working fine(both iOS and android)

2.Device to Air Desktop = Working fine

3.Device to flash player = fail

Please correct me if this is not the current status. Also, could you please update the https://bugbase.adobe.com/index.cfm?event=bug&id=3560258 reported over bugbase with the updated information as from the title it's look like rtmfp is not working on iOS and please update the flash player version you are using. I will let the FP team know about this thread.

Regards,

Nimit

pinter75Author
Known Participant
July 31, 2013

Hi,

The issue is an air 3.5 or later.

Devices can no longer do rtmfp over local wifi to eachother unless they are compiled with the same version of air. Eg 3.4 won't talk to 3.5, but 3.5 will talk to 3.5

This is not so much of an issue.

The biggest issue I am facing is that I cannot get Flash Player (chrome 11,8,800,115)  to talk to the compiled apps using 3.5 or newer.

I get the NetGroup.Connect.Success event, but nothing further.

This occurs using my dev key and cirrus, or over local p2p wifi.

If I compile the app with 3.4 then it works as expected. The issue with this is I cannot upload to the App store with this version.

I don't know if the issue lies with the FP, or Air. It seems that something has changed with the new Air builds, for example on Android it won't send or receive video - unless you quit the connection and try again - then it works. This behaviour is not seen on 3.4

In a nutshell rtmfp works great in 3.4 - anything newer then that and it appears broken.

Regards.

pinter75Author
Known Participant
July 31, 2013

Hi,

I have updated the Bug.

I feel that I am stuck between a rock and a hard place!

I can't submit air 3.4 apps to the Appstore, unless I use minimum 3.7 - but this breaks the product :-(

Hopefully it is something I have missed, but honetly I have been over this with a fine tooth comb, the fact that 3.4 works great is more puzzling.