I just switched to dev channel on my Chrombook(ASUS flip). I got google play and was able to run apps directly but the chromebook didn't show me my own app. The app I wanted to run is an app targetted for tablet devices and in the manifest file, I have android:normalScreens and android:smallScreens set to false and android:requiresSmallestWidthDp="600". Could this be the reason why google play isn't showing me my app on Chromebook? What other reasons are possible? When I try to see the device from my desktop, it just says "This item is incompatible with your device". Thanks.
Related
I created a firebase project. This communicates with a mobile application (node.js). As part of this project I want to use pupeeteer.
I have no problem launching functions using pupeeteer in firebase.
The problem is that I want to make the user perform actions. So I have to display the web page (pupeeteer) in the application via a browser generated by the server (with a firebase function?)?
However I have no idea how to launch a browser instance in the background and close it at the end of processing?
Can you help me ? Is this the right solution?
I want to use this :
This library does 2 things:
Download the chromium binaries and launch a Chromium process.
Connect to this process with Websocket and send json commands to control the browser.
Due to limitations on mobile platforms (iOS and Android), it is not possible to launch an external Chromium process on iOS and Android. So, step 1) does not work on mobile.
You can still use puppeteer-dart on Flutter either with:
Flutter on Desktop (macOS, windows, Linux)
Flutter on mobile BUT with the actual Chrome instance running on a server and accessed from the mobile app using puppeteer.connect
The pub.dev website reports that this library works with Android and iOS. The supported platform list is detected automatically and can't be manually modified to express the current limitations
LOG
Session 'app': Installation did not succeed.
The application could not be installed: INSTALL_FAILED_MISSING_SHARED_LIBRARY
Retry
AVD shows error: missing feature: WATCH
I was working on a project for some time and it was working properly. I recently tried making a few changes and it started showing this error. The app is a normal mobile application
hi this error comes when you try to run your 'wearable' app(=module) on 'mobile' simulator.
if you don't have wearable module in your project,
check if your manifest has something related to the "wearable". if you have, please remove the line
<uses-library
android:name="com.google.android.wearable"
android:required="true" />
check if you have any wearable device on your simulator. if have,
delete
if you have wearable and mobile modules, Understand that
your project has 2 modules. (1. mobile 2.wearble)
run your module on right device ( mobile app on mobile simulator,
wearable app on wearable simulator.)
Trouble Shooting
please check on left side of your device option. you probably
selected wearing app.
make sure that your module (Red Box) is matched with your
simulator(Yellow Box)
I know I nned test the Google in-app purchase of an app in a real mobile phone.
Can I use Android Studio emulator to test Google in-app purchase when I publish the app to Internal test track of Google Play?
Yes, it is no different than with a physical device.
Just make sure your emulator is running an Android OS with Play Services. You can then open Play Store on it, log in with your Google Account (the one in the Internal test track) and then you can test the in-app purchase.
You can learn more about how to test this here. Relevant steps for setting up a device (including an emulator) can be found here.
I know you can work with beacons with a iOS app or Android app.
But you can work with a web app to?
(A website recognize a beacon and do something)
Unfortunately, the general answer is no. You need native components to detect Bluetooth beacons on both Android and iOS. The web browsers on both operating systems have no hooks to detect beacons via JavaScript or HTML.
Chrome OS does have Bluetooth bindings in its Chrome browser, which may allow you to build a web app on Chrome OS that does this. But this would really be a Chrome App not a general purpose web app.
The Chrome browser for iOS and Android also detects Eddystone-URL beacons, but it will not pass the detection info to a web app. Detections are sent to the user as a notification and tapping on that notification simply brings up a configured URL in the Chrome web browser. This does not allow any dynamic web app behavior based on beacon detections.
I have been trying for days to get a simple app any app made in livecode to display either on my tablet, smartphone or emulator. It just doesn't work. Here is what I have done:
I have installed my sdk and pointed livecode to it in preferences.
Picked 2.3 as my version
Check my google usb drivers and they are up to date.
I followed live code's step by step and no success. I am thinking that since I am running windows 7 not a Mac, maybe this cant be done. It seems all the developers run Mac's?
I even tried to make a .apk, It made the file but " There was a problem parsing the package" once I got it on my Galaxy tab. I made sure that I checked the box to allow programs to run on my tablet. So I am still stuck.
To see if the SDK is working correctly you could try to use the Android SDK emulator first.
Open the Android SDK Manager and select the menu Tools->Manage AVDs.
There you can create a virtual Android device and run it.
If the virtual device is running you can see the virtual device under "Development->Test Target in Livecode. Select it and either select "Test" under "Development" or press the "Test" button. Does this work?
That error message means that the operating system on your device is preventing the app from being installed. The most likely reason for this is that you haven't changed the "Allow installation of apps from Unknown Sources" setting on your Galaxy Tab. There are other reasons and solutions for this error message - to see them visit Panagiotis's excellent blog post on the LiveCode website, your error message is in the fifth example
https://livecode.com/how-to-deploy-apps-to-android-devices/