Module not found

Solar2D General Questions/Discussion
#1

Hello.

I’m writing a little app (it’s little so far. Also, I am very new at Corona, so be gentle, please). Works fine in simulator.

Decided to try it on the iPhone. Followed various instructions, made icons, got provisioning profile, did build, installed it on phone. So far so good.

Tried to run on phone, and I get Runtime error concerning module ‘app.myapp’ not found (and it seems to repeat this several times in the various places it looked).

Checked for the problem in various docs. Remembered that the phone is case sensitive and corrected that.

Here’s the odd thing: The message reports it can’t find “app.myapp,” but the folder is named “App” (with the uppercase A). I have checked, and all the references to anything in the App folder are using App (not app).

What gods have I offended?

-Bob in Minneapolis

#2

An update:

I changed the name of myApp.lua to theApp.lua and also changed the name in the require statement. Rebuilt, reinstalled. 

App shows up on the phone.

Now, I have the same problem with another file. 

Why changing the name helped I don’t know.

I will post results as I find them.

-Bob

#3

Solved (though it does not make much sense).

I changed the name of the other file that was having issues. Made sure to save all files.

Things are ok (at least with respect to this problem).

-Bob

#4

Bob,

Hi.  I’m not getting enough context here unfortunately.  If you have a problem like this in the future, you might try zipping up the whole project (source and images, etc.) and sharing it via dropbox so we can look it over.  

It’s hard sometimes to figure out what trouble folks are having because:

  1. While they are doing their best to describe the problem as they see it (you did this).
  2. The problem may be totally unrelated to the issue they see.
  3. We can’t see the whole picture.

I know its a pain, but sometimes letting us see the whole thing is the easiest way to figure it out.  Of course, as you get better (and you will), you’ll better understand the source of issues and your questions will be easier to ask and answer.

Cheers,

Ed

#5

Ed,

Thanks for the input. I seem to have resolved the problem: I renamed the two files that were causing the problem (and modified the require statements). Then, I carefully saved everything. Seems to have fixed it.

I must say that everyone in the forum has been very helpful (and tolerant).

Thanks for the info.

-Bob

#6

Sure thing Bob, but that solution is ‘weird’ and sounds like a different error.  So, again, if you run into this or other hard to understand issues in the future, consider my above suggestion.

Cheers,

Ed

#7

An update:

I changed the name of myApp.lua to theApp.lua and also changed the name in the require statement. Rebuilt, reinstalled. 

App shows up on the phone.

Now, I have the same problem with another file. 

Why changing the name helped I don’t know.

I will post results as I find them.

-Bob

#8

Solved (though it does not make much sense).

I changed the name of the other file that was having issues. Made sure to save all files.

Things are ok (at least with respect to this problem).

-Bob

#9

Bob,

Hi.  I’m not getting enough context here unfortunately.  If you have a problem like this in the future, you might try zipping up the whole project (source and images, etc.) and sharing it via dropbox so we can look it over.  

It’s hard sometimes to figure out what trouble folks are having because:

  1. While they are doing their best to describe the problem as they see it (you did this).
  2. The problem may be totally unrelated to the issue they see.
  3. We can’t see the whole picture.

I know its a pain, but sometimes letting us see the whole thing is the easiest way to figure it out.  Of course, as you get better (and you will), you’ll better understand the source of issues and your questions will be easier to ask and answer.

Cheers,

Ed

#10

Ed,

Thanks for the input. I seem to have resolved the problem: I renamed the two files that were causing the problem (and modified the require statements). Then, I carefully saved everything. Seems to have fixed it.

I must say that everyone in the forum has been very helpful (and tolerant).

Thanks for the info.

-Bob

#11

Sure thing Bob, but that solution is ‘weird’ and sounds like a different error.  So, again, if you run into this or other hard to understand issues in the future, consider my above suggestion.

Cheers,

Ed