Build 2013.1017: Requiring external modules broken

When requiring my external module local app = require("appglobals"), the build 1017 throws this error:

[text]
2013-01-30 23:33:12.271 Corona Simulator[71365:707] module ‘appglobals’ not found:resource (appglobals.lu) does not exist in archive
no field package.preload[‘appglobals’]
no file ‘(null)/appglobals.lua’
no file ‘/Applications/CoronaSDK/Corona Simulator.app/Contents/Resources/appglobals.lua’
no file ‘/Library/Application Support/Corona/Simulator/Plugins/appglobals.dylib’
no file ‘./appglobals.dylib’
no file ‘/Applications/CoronaSDK/Corona Simulator.app/Contents/Resources/appglobals.dylib’
[/text]

I’m thinking it must have something to do with ‘(null)/appglobals.lua’ in the output above, right?
Corona isn’t looking in the current directory for the file ‘./appglobals.lua’.

Build 2013.1016 is OK. [import]uid: 70847 topic_id: 35456 reply_id: 335456[/import]

I can confirm this happens also for the Text_Candy lib file won’t load with the same error [import]uid: 8697 topic_id: 35456 reply_id: 140905[/import]

I have the same error with text_candy lib, version 1016 works perfect.
[import]uid: 96270 topic_id: 35456 reply_id: 140929[/import]

Happens with my own written libs as well. Seems as if the wrong directory is looked at. [import]uid: 101883 topic_id: 35456 reply_id: 140934[/import]

It turns out we did introduce a bug in build 1017 that broke the “require” module. We fixed the issue and it should be available in the next daily build (1018?).

Thanks,
Tom [import]uid: 7559 topic_id: 35456 reply_id: 140946[/import]

I can confirm this happens also for the Text_Candy lib file won’t load with the same error [import]uid: 8697 topic_id: 35456 reply_id: 140905[/import]

I have the same error with text_candy lib, version 1016 works perfect.
[import]uid: 96270 topic_id: 35456 reply_id: 140929[/import]

Happens with my own written libs as well. Seems as if the wrong directory is looked at. [import]uid: 101883 topic_id: 35456 reply_id: 140934[/import]

It turns out we did introduce a bug in build 1017 that broke the “require” module. We fixed the issue and it should be available in the next daily build (1018?).

Thanks,
Tom [import]uid: 7559 topic_id: 35456 reply_id: 140946[/import]