Fire 8.4.96.2059D and TableView iOS sample problem

When run a default TableView example project from Fire the following error occurs:

An exception occurred in AppTableView2,
thread 4ee22

Type:

Message:

EXC_BREAKPOINT (code=EXC_I386_BPT, subcode=0x0)

Call Stack:

000000000005a001, dyld_sim, ,dyld_fatal_error, dyld_fatal_error()
000000000005c651, dyld_sim, ,dyld::halt(char const*), dyld::halt(char const*)()
000000000005e0c6, dyld_sim, ,dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*), dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*)()
000000000005a1f9, dyld_sim, , start_sim, start_sim()
00000000001084b4, dyld, , dyld::useSimulatorDyld(int, macho_header const*, char const*, int, char const**, char const**, char const**, unsigned long*, unsigned long*),
dyld::useSimulatorDyld(int, macho_header const*, char const*, int, char const**, char const**, char const**, unsigned long*, unsigned long*)()
00000000001068f7, dyld, , dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*), dyld::_main(macho_header const*,
unsigned long, int, char const**, char const**, char const**, unsigned long*)()
0000000000102200, dyld, , dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*), dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*)()
0000000000102047, dyld, , _dyld_start, _dyld_start()

Fire 8.4.96.2059D
XCode 8.1
Simulator iPad 2 9.3

Best regards,
Jose A.

Which language?

Oxygene

It does not work with any language.
The XCode works perfectly.

Not sure what to tell ya. I can’t reproduce this.

What strange things. :confused:

Just did a quick test to create/run a default TableView project with Fire 8.4.96.2059D, but can’t reproduce the issue, there’s no error.

1 Like

Ok. Thanks James.

Marc,
I have installed Xamarin Studio on the MAC.
Can it influence Fire?
It gives the sensation that Fire in my MAC does not compile the application correctly, since, being installed the application in the simulator, if I click on its icon it can not be started either.

Can the version of Mono installed by Xamarin Studio affect Fire?

A reinstallation of Fire does not solve the problem.

I have xamarin studio installed and I’m not seeing any problems.

You do mention you have Simulator iPad 2 9.3. Have you tried with a simulator that has 10.x ?

No. I’m reinstalling the OS to see if everything works ok.
I’ll tell you something. :grin:

Marc,
I have reinstalled the operating system for nothing.
After reinstalling it, configuring it, installing XCode 8.1, installing Fire, the error still occurs, but I have verified that it only occurs if I launch the application to simulator iPad 2 iOS 9.3.
If I launch it, for example, to an iPad Air 10.1 then the application is shown in the simulator without problems.
If I launch an application with the XCode 8.1 to the simulator iPad 2 iOS 9.3 everything works correctly, so it is not a problem of the simulator.
This makes it assume that Fire has a bug when using an iPad 2 9.3 simulator :cold_sweat:

Yes, with a simulator 10.1 everything works correctly. Thank you John, apparently it’s a Fire bug with a 9.3 simulator

i don’t see how :frowning:

hmm. are you setting the deployment target to allow running on 9?

Great. So its the iOS version ?

When you build in Fire what version of iOS do you have in settings ?

No, I thought I was picking it by default, and from what I see it is blank.
I think Fire should indicate this with a warning message. :confounded:

Target version: iOS
Deployment Target: Blank
:confounded:

Fwiw, i get the same/similar behavior as you if i do NOT set a deployment target (i.e. if i build my app for iOS 10.x only, and try to run on a 9.3 Simulator. As soon as i adjust the deployment target to 9.0, it runs fine.

So i’d consider this "as designed.

With XCode, Xamarin or Delphi this does not happen, so do not mislead the users, they make the necessary automatic adjustments so that these types of errors do not occur. Also, at a minimum, Fire should indicate to the user that field is empty. Do not you think?