I'm really stuck here. Brand new install on linux . SDK platform is Q.
I create a virtual device and choose on e with the Play store logo. Pixel 2 , Nexus 5.
All good
I activate and the device pops up. I select more options(...)Location is working great. I select Google play. Now it displays "Loading.." forever. If I click update. It crashes with the following error. "There was an unknown error while opening Google Play services Page."
????
Has anyone seen this. Any idea what i can try?
Related
After accidentally pushing update on Package manager my tizen Studio stop functioning the way it did before.
I had to remove all my IDE files and install from scratch
After 1 week struggling i managed to install the recent Extention 6.5 and my Extention 4.0 for My tizen smart tv 2.4
Now im connecting to the same tv and stuck in this for about 4 minutes before the app starts:
`
Launching the Tizen application...
# If you want to see the detailed information,
# please set the logging level to DEBUG in Preferences and check the log file in '/Users/ANYNO/tizen-studio-data/ide/logs/ide-20221229_161441.log'.
[Initializing the launch environment...]
RDS: On
Target information: UE55KU6075
Application information: Id(HV7Ga7JLUO.SoleimanTV), Package Name(HV7Ga7JLUO), Project Name(SoleimanTV)
[Transferring the package...]
`
I took stopwatch and its taking 4,20 min to "transfer the package to the tv"
at the same time the certificate i created for my samsung tv in CF MANAGER should work for my Emulator also?
My questions are:
Why taking so long for pushing the app to the remote tv? what im doing wrong?
Should i create two different certificate one for TV and one for emulator?
Please respond if you have experienced the same. I would otherwise not have other solutions than reset my MAC and start all over again.
PS: friendly advice: IF you ever see a button with the text "Updates available" STAY AWAY
Uninstalled Tizen Studio and installed all over again.
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)
why I am getting this error when I am trying to run my application in real device not simulator
ApplicationVerificationFailed: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ttjwEf/extracted/DSP.IOS.app : 0xe8008016 (The executable was signed with invalid entitlements.)
error MT1006: Could not install the application '/Users/macbookpro/Documents/gitProject/DSPMobileGit/DSP.Mobile/DSP.iOS/DSP.IOS/bin/iPhone/Debug/device-builds/iphone6.2-9.3.5/DSP.IOS.app' on the device 'Mohamed’s iPhone': Your code signing/provisioning profiles are not correctly configured. Probably you have an entitlement not supported by your current provisioning profile, or your device is not part of the current provisioning profile. Please check the iOS Device Log for details (error: 0xe8008016).
here steps I did to run my app
First I created project in Xcode with same bundle name and let Xcode handle Provisioning
when I tried to run in Visual studio it dosent work
Second I create manual provisioning with wild id but it dosent work
I note something each time I set my signing identity and provisioning profile , when I back to screen I find it back to none again
may be that is the reason
Using Visual Studio for Mac 2019
First, determine whether the problem is entitlements. Find tab "Deploying to Device", and look at the full message starting with
"ApplicationVerificationFailed: Failed to verify code signature of ..."
Look for:
... The executable was signed with invalid entitlements.
In that case, see https://stackoverflow.com/a/43055084/199364.
The below answer is for the other likely situation:
... no valid provisioning found for this device.
On newer versions of Visual Studio for Mac + Xamarin iOS (or Xamarin Forms, deploying to iOS):
Connect the phone to Mac via USB cable.
Popup on phone, select "Trust" this computer.
In VS, Open Info.plist.
Make sure the "Application" tab is selected at the bottom of the pane.
Select "Automatic Provisioning".
Follow the instructions.
When successful, you'll see (below "Automatic Provisioning" radio button):
Apple ID: your-apple-id-email
Team: your-company-name-or-your-developer-name
(Green checkmark) Ready to deploy app to connected device.
IMPORTANT:
Even if you have previously setup Automatic Provisioning for a different device, you still need to open Info.plist / Application tab after attaching this new device. (After doing this once per device, you can switch which device is attached, without repeating.)
If Xcode has never seen the device before, it can take MINUTES before Xcode has validated it and attached it. See following paragraph if you'd rather see Xcode giving you a message about what its doing (and spinning a busy indicator). Won't be any faster, but is more obvious that something useful might be happening. (On older Xcodes, people have reported delays up to 10-15 minutes.)
If having trouble getting it to see your phone, google for instructions to open XCode and add your phone as a device known to XCode (XCode menu Windows / Devices and Simulators / Devices tab). That is, it may be easier to first get it working under XCode, then go back to VS, disconnect and reconnect the cable to phone, try instructions above again.
Using Visual Studio (Windows) 2022
Personally, I always FIRST get the phone|tablet recognized using XCode, connecting it to Mac. See instructions above.
Then:
Connect device to PC.
Automatic Provisioning is found in YourApp.iOS / Properties / iOS Bundle Signing.
Select Team.
if it works => "Automatic provisioning completed successfully."
OPTIONAL:
Disconnect device from PC, connect it to Mac - should be listed under "Remote Devices" in VS on Windows.
TBD: Not sure why I failed to get it to be listed as a Local Device, when it was attached to PC.
I had the same issue in a Xamarin.iOS project. I found a workaround. The reason was the update from Xamarin.Swift4 package 4.0.0.1 to 4.0.0.2.
After I downgraded back to 4.0.0.1 the issue no more exist.
I created an issue report at github: https://github.com/Flash3001/Xamarin.SwiftSupport/issues/25
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/
I have a PhoneGap app that works perfectly on the iPhone 3.2 simulator and also iPhone 3 and 3GS devices.
I have just downloaded and installed the latest iOS SDK, changed the settings in Project>Edit Project Settings to allow the application to work, and run it successfully within the iPhone 4 simulator and even the iPad simulator.
However when I run it on a provisioned iPhone 4 device, nothing seems to happen when I run it. I get the splash screen, but nothing happens after that. In the log I get this:-
2010-09-13 10:11:34.156 MyApp[89:307] Going to play default movie
2010-09-13 10:11:34.169 MyApp[89:307] Can't find filename default.mov in the app bundle
2010-09-13 10:11:34.948 MyApp[89:307] Device initialization: DeviceInfo = {"name":"iPhone","uuid":"548444a41eee3aec9dd66511e12e6a6b1b277a2a","platform":"iPhone","gap":"0.9.0","version":"4.0.2"};
2010-09-13 10:11:35.022 MyApp[89:307] Docs Path:/var/mobile/Applications/D887FEA7-0C56-4991-890F-E790361A9D64/Documents
2010-09-13 10:11:35.037 MyApp[89:307] Free space is 15497396224
And nothing else!!
Really annoying. Anybody know what might be happening here? I tried fiddling with a few settings in the Project Settings but that doesn't seem to have fixed it.
Any help would be really appreciated.
Regards
Nick
Update - my problem. I had some external javascript which was crashing due to the way I was calling it from the HTML file. Weird that it only affected the iPhone/iPad device but not the simulators, but there you go....