I am getting this error in my app and I can not figure out why.
that apps works beautifully in the Windows Android simulator no errors generated what so ever - everything works like a champ.
I put the app on the device and I receive this error
?:0: attempt to index a nil value -
anyone ever see this before? and know what the issue may be?
thanks in advance
Larry [import]uid: 11860 topic_id: 36048 reply_id: 336048[/import]
It would be helpful to see some more info with a stack traceback.
It should look something like this example:
-- example start --
Runtime error
?:0: attempt to index a nil value
stack traceback:
[C]: ?
?: in function 'xyz'
...sx7vhhg96sjffvw0000gn/T/TemporaryItems/7/abc.lua:123: in function <...sx7vhhg96sjffvw0000gn><br>?: in function <?:215><br>-- example end --<br> [import]uid: 70847 topic_id: 36048 reply_id: 143204[/import] </…sx7vhhg96sjffvw0000gn>
The simulator is not generating any errors so there is no stack trace back.
The app is dying on the actual device…
simulator works like a charm.
That’s the problem.
Simulator works with no errors device crashes.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143248[/import]
Issue Resolved.
The problem was that the “WINDOWS simulator is not case sensitive for file names”
The Mac / Android Devices / and IOS is case sensitive.
thanks for the follow up.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143249[/import]
Most Mac’s are not case sensitive either. [import]uid: 199310 topic_id: 36048 reply_id: 143259[/import]
really? is that a mac setting?
ill leave it as it will catch my screw ups 
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143281[/import]
Mac’s HFS+ file system has always been case insensitive as far as I know until either Lion or Mountain Lion and now there is an option to format drives with case sensitivity turned on.
So I don’t know if new Macs are by default formatted with this flag turned on, but older Macs that have been upgraded over the years are insensitive by default.
[import]uid: 199310 topic_id: 36048 reply_id: 143398[/import]
It would be helpful to see some more info with a stack traceback.
It should look something like this example:
-- example start --
Runtime error
?:0: attempt to index a nil value
stack traceback:
[C]: ?
?: in function 'xyz'
...sx7vhhg96sjffvw0000gn/T/TemporaryItems/7/abc.lua:123: in function <...sx7vhhg96sjffvw0000gn><br>?: in function <?:215><br>-- example end --<br> [import]uid: 70847 topic_id: 36048 reply_id: 143204[/import] </…sx7vhhg96sjffvw0000gn>
The simulator is not generating any errors so there is no stack trace back.
The app is dying on the actual device…
simulator works like a charm.
That’s the problem.
Simulator works with no errors device crashes.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143248[/import]
Issue Resolved.
The problem was that the “WINDOWS simulator is not case sensitive for file names”
The Mac / Android Devices / and IOS is case sensitive.
thanks for the follow up.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143249[/import]
Most Mac’s are not case sensitive either. [import]uid: 199310 topic_id: 36048 reply_id: 143259[/import]
really? is that a mac setting?
ill leave it as it will catch my screw ups
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143281[/import]
Mac’s HFS+ file system has always been case insensitive as far as I know until either Lion or Mountain Lion and now there is an option to format drives with case sensitivity turned on.
So I don’t know if new Macs are by default formatted with this flag turned on, but older Macs that have been upgraded over the years are insensitive by default.
[import]uid: 199310 topic_id: 36048 reply_id: 143398[/import]
It would be helpful to see some more info with a stack traceback.
It should look something like this example:
-- example start --
Runtime error
?:0: attempt to index a nil value
stack traceback:
[C]: ?
?: in function 'xyz'
...sx7vhhg96sjffvw0000gn/T/TemporaryItems/7/abc.lua:123: in function <...sx7vhhg96sjffvw0000gn><br>?: in function <?:215><br>-- example end --<br> [import]uid: 70847 topic_id: 36048 reply_id: 143204[/import] </…sx7vhhg96sjffvw0000gn>
The simulator is not generating any errors so there is no stack trace back.
The app is dying on the actual device…
simulator works like a charm.
That’s the problem.
Simulator works with no errors device crashes.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143248[/import]
Issue Resolved.
The problem was that the “WINDOWS simulator is not case sensitive for file names”
The Mac / Android Devices / and IOS is case sensitive.
thanks for the follow up.
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143249[/import]
Most Mac’s are not case sensitive either. [import]uid: 199310 topic_id: 36048 reply_id: 143259[/import]
really? is that a mac setting?
ill leave it as it will catch my screw ups
Larry [import]uid: 11860 topic_id: 36048 reply_id: 143281[/import]
Mac’s HFS+ file system has always been case insensitive as far as I know until either Lion or Mountain Lion and now there is an option to format drives with case sensitivity turned on.
So I don’t know if new Macs are by default formatted with this flag turned on, but older Macs that have been upgraded over the years are insensitive by default.
[import]uid: 199310 topic_id: 36048 reply_id: 143398[/import]
It would be helpful to see some more info with a stack traceback.
It should look something like this example:
-- example start --
Runtime error
?:0: attempt to index a nil value
stack traceback:
[C]: ?
?: in function 'xyz'
...sx7vhhg96sjffvw0000gn/T/TemporaryItems/7/abc.lua:123: in function <...sx7vhhg96sjffvw0000gn><br>?: in function <?:215><br>-- example end --<br> [import]uid: 70847 topic_id: 36048 reply_id: 143204[/import] </…sx7vhhg96sjffvw0000gn>