I just downloaded ES File Explorer, now I can see it and it works.
Thanks for the info! [import]uid: 50459 topic_id: 34133 reply_id: 135921[/import]
No problem, glad I could help. [import]uid: 84115 topic_id: 34133 reply_id: 135922[/import]
thanks for the replies Rmbsoft & Alan
adding "game’.apk after ./adb install didn’t work.
And ‘Allow for installation of Applications’ was set to on.
I’m pretty green at this, so it’s frustrating, because it’s probably something I have/or haven’t done, but can’t be sure.
I will try the ES File Explorer you mention and let you know how it works out.
thanks,
Bill [import]uid: 97864 topic_id: 34133 reply_id: 135930[/import]
@billiamsw how experienced are you with the command line environment? The reason I ask, is I don’t see your your adb command is going to work.
When you put a ./ in front of a command like adb, that is explicitly telling the command shell to execute the program from the current directory. Since adb is running, that tells me you are in the folder/directory where the adb command lives.
Unix commands are typically in the format of:
/path/to/command options /path/to/file
Since ./ tells me your in the adb tools folder, is the apk you’re trying to install in the same folder? By not specifying a path to the file and just the file name, the assumption is the file is in the same folder as the command which is probably not the case and probably not a best practice either.
There are two solutions to this. First make sure your adb command is in a path the system can find it. You can do an “echo $PATH” command (without the quotes) and get a list of paths separated by the colon (
character. If the folder where the adb tools lives is listed there then you’re in great shape. If the adb tools folder is listed, then do a “cd” command to change directory to where your .apk file lives and enter the command as such:
adb install yourapp.apk
where yourapp is the name of your app. If it has spaces in the file name, put it in quotes like:
adb install “your app.apk”
If the adb command is not in the path you can do:
./adb install /path/to/yourapp.apk
and install it that way. You should get messages about a server starting up, a bit of a pause then it should come back and say success.
Now here is the really fun part. Lets say you make another build, this command will fail because ADB will not let you write over an existing app. You have to do a:
adb uninstall com.yourbiz.yourapp
where com.yourbiz.yourapp is the string you use to identify your app. Not the file name. Once it’s uninstalled, then you can run adb install to put the new version on.
[import]uid: 199310 topic_id: 34133 reply_id: 135996[/import]
Hey Rob,
Wow. Thanks for your input!
I am a newbie to this. I got this far jumping through blogs from Corona and Amazon Developer. Maybe because I am green, I find the Mac OS directions not specific to follow and more than a little confusing. Especially compared to building for iOS.
my path looked like this:
~ billwesterfield$ /Applications/adt-bundle-mac/sdk/platform-tools/./adb install/~ billwesterfield$ /Desktop/myapp.apk
Any resources you could recommend for a app developer newbie working on a Mac to guide?
I will check out your options when I get home to my work computer.
Thank you.
Bill [import]uid: 97864 topic_id: 34133 reply_id: 136000[/import]
Downloaded Easy Installer and when I fired it up my test app appeared in downloads folder (I had placed it there using the Android Utility Transfer).
Thanks everyone.
Will more than likely be back when I am ready to submit the final app.
Merry Christmas,
Bill
[import]uid: 97864 topic_id: 34133 reply_id: 136014[/import]
Just an addition to you apk instructions Rob, to overwrite an app you can use:
adb install -r yourapp.apk
Slightly quicker than uninstalling + reinstalling. Definitely works on Nook, not sure about other devices but I would assume they work too. [import]uid: 84115 topic_id: 34133 reply_id: 136015[/import]