Generally, you shouldn’t be renaming font files. There is an internal name and its kind of best if those names match. But that’s beside the point. It’s a change you made and perhaps something is amiss with that. I don’t know if you’re hitting a case sensitivity issue or what, but you’re not providing any messages from your device’s console log that could clue us into what’s going on. We really need your help to help you.
Rob
@rob
I’m reading but not find how to view messages from my device’s console log. Any link to read how to achieve this task?
https://docs.coronalabs.com/guide/basics/debugging/index.html
==> https://docs.coronalabs.com/guide/basics/debugging/index.html#device-debugging-android
I remember when I develop for Blackberry you can test the build in a virtual devices. There is a way I can install a Note 8 virtual device? Right now I do not have the real device in my hand.
Testing in virtual devices is very slow. Get a real device to save yourself a ton of pain.
Also, a virtual device won’t 100% replicate testing on a real device, so you may simply be wasting your time if you go that route.
Hi again!
Today I install the .apk to my Samsung Galaxy tab A via adb in which I explain I can’t installed via my normal installation process (Corona simulator built + make a .rar + send via email + install in my Nexus 6 … then upload the .apk file to Google Drive, not the .rar, and send the link to other devices via email, message, etc).
My questions:
If I have managed to install the .apk without any problem through adb can I continue with the publication of my app?
The error was in the devices not in my code?
Thanks in advance
DoDi
You’re asking questions that are impossible to answer. You are talking about problems on a Note 8, but now you’re talking about a Galaxy Tab A. You can publish your app when you are confident that you’ve tested it and you are not expecting any problems. We can’t answer that for you.
I doubt your devices were the problem. I don’t know if it’s your code either. Maybe an issue with using RAR?
Do you have a device where you’re getting the error? If you do, maybe try installing the way that’s broken, but have it tethered via USB and use “adb logcat” and have that running before you install it and then watch for errors.
Rob
I’m talking about a weird installation on a note 8 devices, that’s the title of the topic. I do not have a note 8 at hand, they were friends that help me. Now, I have a tab A, that I realized after having created the topic, that I confront installation problems, is written above in this topic. so as not to create another topic with the same situation, I decided to write it here.
After a hard morning trying to collect errors at the time of installation, I managed to install the apk using the adb in my Galaxy Tab A. As I am a newbie I thought that someone could have gone through the same situation and could help me. @Rob I am not a programmer, I am beginning to understand how Corona’s api work and my main intention is to maintain good relations with the members of the forum. If I’m doing something wrong I apology.
The apk was successfully installed, with no errors, in my Galaxy Tab A via adb, but I still can’t install it via the google drive method describe above too.
Thanks in advance
DoDi
All is good community wise. I was just pointing out that no one can answer if you can continue to publish your app. Only you can make that decision. Release when you’re comfortable.
And for question #2, is it your code or a problem with the device? That’s hard to answer too because we don’t have enough information.
Rob