I am built a Windows Phone application with PhoneGap Build and I am trying to install it into a Nokia Lumia 625 with Software: Windows Phone 8.1.
I have installed the application on a Nokia Lumia 735 with Software: Windows 10 Mobile with no problems, for the Lumia 625 things seems much more complicated :(
To install the App on the Lumia 625, those should be the steps:
1 - Download the application with extension .xap
2 - Copy the file into the phone SD card
3 - Go to the Windows Phone Store
4 - Click the 3 dots on the bottom-right corner
5 - Click on 'Install local apps'
At that point my application should be listed there and I should be able to install it.
My current problem is that after step 4, the option 'Install local apps' is not visible...I have download WhatsApp.xap from internet and when it is added to the SD Card that option shows up and I am able to install the application.
The above tells me that there is something wrong with my application but I don't understand what. Below there is a screenshot of what I have loaded into the SD Card: http://prntscr.com/h7a7d8
The current state is:
- if both App are in the SD Card, 'Install local apps' is shown but only WhatsApp is listed
- if I remove WhatsApp from the SD Card, 'Install local apps' is not shown
Can anyone help me to understand what could be wrong in my App to not being able to install it into Lumia 625 but working fine on the Lumia 735?
Please let me know if you guys need any further information as the config.xml or anything else and I'll be able to provide it
Thanks
I have at the end managed to solve this problem myself, I have opted for a different way to install the app.
By installing Windows 10 SDK, I had at my service a tool called 'Windows Phone Application Deployment 8.1' and to get it to work I just need to connect the Phone through USB cable, select the APPX file I want to upload install to the phone and 'DEPLOY' :)
Here is a screenshot: http://prntscr.com/h7qdxj
Thanks guys anyway :)
Related
An IPA file is generated from Xcode Version 7.3.1 (7D1014) and I would like to install it onto an iPhone running iOS 10, but nothing happens after I click the install button.
I uploaded it to dropbox using Betabuilder for iOS apps.
That IPA file can be installed on iOS 8.x and iOS 9.x. I tried searching for this issue online and I cannot find a solution.
In Betabuilder for iOS apps need following files
App's Icon
Project.ipa
index.html
manifest.plist
The problem i cannot install app in iOS 10 is I forget to add project name in manifest.plist. But apps can be installed in iOS 9,8.
Please see the screen shot below.
I'm aware the deadline for the developer kit for AppleTV has now passed some time ago.
What I'm confused by is, is it not possible to test tvOS apps on the actual AppleTV itself?
Is it possible to say hook up your mac with the tv device via HDMI and test it that way, like the way you do with other apps?
Many thanks
The dev kit is an actual AppleTV and was recently updated to the official tvOS release. You can test tvOS apps on it (or any other AppleTV) by connecting it to your Mac with a USB-C cable.
I have made a video showing how to test an app in Apple TV with TestFlight. https://youtu.be/Bsgdnl3dd4U .
Install TestFlight in your Apple TV first
Use "redeem code" to be able to see the apps in your TestFlight
Afterwards, you can see your beta versions on TestFlight.
To run your tvOS app on an AppleTV on your local wifi network:
On your AppleTV go to Settings > Remotes and Devices > Remote App and Devices.
In Xcode open Window > Devices and Simulators. You should see your AppleTV listed there.
Press the 'Pair' button and fill the 6 digit code shown on the tv.
Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome's remote debugging for android (more details here).
I have the developer options and USB debugging enabled on my phone, and this worked perfectly fine on android 4.1.2.
Now, when I connect my phone to my PC, it simply connects as a media storage device and is not discovered as a USB device by chrome.
I am ruling out any problems with chrome as I could USB debug with a Google Nexus4, also, looking at some other thread (here and elsewhere) it seems to be a problem with Samsung's 4.3 upgrade.
Any pointers to get this working?
My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.
I downloaded the SDK and followed the instructions at Chrome Developers. How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8:
Download Android SDK here ("SDK Tools Only" section) and unzip the content.
Run SDK Manager.exe and install Android SDK platform tools
Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
Enter the path with ex:
cd c:/downloads/sdk/platform-tools
Open ADB by typing in adb.exe
Run the following command by typing it and pressing enter:
adb devices
Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ")
"adb kill-server"
"adb start-server"
"adb devices"
I had major problems and managed to get it working with these steps. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB.
Update
If you are using Windows 10 and couldn't find the link to download Android SDK; you may skip #1 and #2. All you need is activate "Android Debug Bridge". Go straight to #3 - #7 after download and execute "platform-tools"(https://developer.android.com/studio/releases/platform-tools.html)
Having attempted to follow Valros.nu's answer, i discovered that the sdk download is now bundeled with androind studio, in an 840MB exe installer.
As all you need for this particular program is the adb program, you can get this in a standalone installer from the xda guys:
http://forum.xda-developers.com/showthread.php?t=2317790
Note that you do not need to type adb.exe, simply type adb devices into the command prompt that is launched after install.
Also, i had to unplug and replug in my samsung s4 to get the remote debugging prompt to appear on the phone
After looking around a little longer I came across this. Apparently, there isn't a solution to this issue yet, but there is a workaround - going back to the legacy workflow.
The legacy workflow did work for me, and the only additional thing I had to do was to go to the platform-tools folder from android SDK download, open a command window here and run command "adb devices".
This caused the computer RSA key fingerprint panel to pop on my mobile screen, and after granting permission, the device showed up under Chrome's Inspect page.
Turns out that it was not an issue caused by mobile OS upgrade but by Chrome (I was thrown off by the fact that it worked on my Nexus4 somehow).
In the older versions of Chrome there was't a need to download the 500 odd mb Android SDK, as it supported an ADB plugin. But with latest version of Chrome, I guess, going legacy is the only way to go.
I have Samsung Galaxy S3 and it was not showing in the "Remote devices" tab nor in chrome://inspect.
The device did show in Windows's Device Manager as GT-I9300, though.
What worked for me was:
Plug the mobile phone to the front USB port
On my phone, click the notification about successful connection
Make sure the connection type is Camera (PTP)
On my Windows machine, download installer from https://github.com/koush/UniversalAdbDriver
Run it :)
Open cmd.exe
cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
adb devices
Open Chrome in both mobile phone and Windows machine
On Windows's machine navigate to chrome://inspect - there, after a while you should see the target phone :)
I'm not sure if it affected the whole flow somehow, but at some point I've installed, and later uninstalled the drivers from Samsung: http://www.samsung.com/us/support/downloads/ > Mobile > Phones > Galaxy S > S III > Unlocked > http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads
For me the solution was to download the Android SDK and launch adb devices which started the adb daemon.
I know this is an older question, but I thought I would also post my solution:
Update your Chrome on your phone and on your PC.
Even if it says you have the latest driver for your device inside
Device Manager, you may need an alternative. Google latest Samsung drivers and try updating your drivers.
I had success after using ade.exe as explained above, plus using the latest version of Chrome Canary. Apparently your desktop version of Chrome has to be higher than the version running on your Android device.
For me, the menu item Inspect Devices wasn't available (not shown at all). But, simply browsing to chrome://inspect/#devices showed me my device and I was able to use the port forward etc. I have no idea why the menu item is not displayed.
Phone: Android Galaxy S4
OS: Mac OS X
In case it helps anyone I will post what worked for me.
I had to plug my S3 into a direct USB port of my PC for it to prompt me to accept the RSA signature. I had my S3 plugged into a hub before then.
Now the S3 is detected when using both the direct USB port of the PC and via the hub.
NOTE - You may need to also run adb devices from the command line to get your S3 to re-request permission.
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
9283759342847566 unauthorized
...accept signature on phone...
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
9283759342847566 device
Those who updated their device to Android 4.2 Jelly Bean or higher or
having a 4.2 JB or higher android powered device, will not found the
Developers Options in Settings menu. The Developers Options hide by
default on 4.2 jelly bean and later android versions. Follow the below
steps to Unhide Developers Options.
Go to Settings>>About (On most Android Smartphone and tablet)
OR
Go to Settings>> More/General tab>> About (On Samsung Galaxy S3,
Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and other galaxy
Smartphone and tablet having Android 4.2/4.3 Jelly Bean)
OR
Go to Settings>> General>> About (On Samsung Galaxy Note 2,
Galaxy Note 3 and some other Galaxy devices having Android 4.3 Jelly
Bean or 4.4 KitKat)
OR
Go to Settings> About> Software Information> More (On HTC One or
other HTC devices having Android 4.2 Jelly Bean or higher)
2. Now Scroll onto Build Number and tap it 7 times repeatedly. A message will appear saying that u are now a developer.
Just return to the previous menu to see developer option.
Credit to www.androidofficer.com
If i check the capability "Shared Used Certificates" in the Windows Phone 8.1 application manifest i get the following error:
Error : DEP0001 : Unexpected Error: Package could not be registered.
(Exception from HRESULT: 0x80073CF6)
Manifest
<Capability Name="sharedUserCertificates" />
I am trying to deploy to a Nokia Lumia Icon with Windows Phone 8.1 developer preview.
Any idea what i am doing wrong or what prereq is not met?
I was able to deploy my app to the emulator, but not to a real device. I got the same error. I asked my contacts at the Phone Team and they said this is a bug and will be fixed with the post RTM updates. It should definitely be possible to sideload apps using the 'sharedUserCertificates' to real devices for normal app developers.
Getting such an app deployed through the Store may be restricted, though. This scenario is primarily meant for enterprise apps, deployed within enterprises.
I wrote a blog post about this.
If I set my phone to install apps to the phone it works just fine. If I switch it back then I get the error.
It has something to do with SD cards!! Not the SD cards per-se , but the mech The only thing different was I installed a new SD card this weekend to my Lumia 1520 with Developer Unlock. I am running VS 2013 Update 4 and have a StandAlone Phone application using a Windows 8.1 shared app class. It was working before and now its not. same error as MAGNUS
With save apps to SD CARD setting in storage sense set
If you use verbose build output it eventually says:
2>Follow the phone setting 2>Phone setting says apps to be installed
to SD card 2>layout root folder:
D:\WPSystem\SharedData\PhoneTools\AppxLayouts
With save apps to PHONE card setting in storage sense
If you use verbose build output it eventually says:
2>Follow the phone setting 2>Phone setting says apps to be installed
to internal storage 2>layout root folder:
C:\Data\SharedData\PhoneTools\AppxLayouts
search your Detailed or "verbose" build output for the term "Phone setting says"
That will get you close. Good luck.
I can confirm that VS 2013 Update 4 causes the error:
Error : DEP0001 : Unexpected Error: Package could not be registered.
(Exception from HRESULT: 0x80073CF6)
My application was deploying to the phone fine before the update, and started failing immediately after the update. Modifying settings:
Settings/Storage Sense/Store New apps on my: phone
Solved the problem. Thanks Matt for the tip, saved me alot of time.
Try to uninstall current application in your phone, and run agian.
For me its solved
This problem can be related to re-use of the same app template on Windows Phone (does not affect Windows desktop apps). In the Windows Phone section of the solution explorer, find your app manifest file (Package.appxmanifest), and review the following line near the top of the file (#'s in this example are representative, not actual):
<mp:PhoneIdentity PhoneProductId="12345678-1234-1234-1234-123456789ABC" PhonePublisherId="00000000-0000-0000-0000-000000000000" />
If you have re-used the same app template, then the PhoneProductId number must be different from one iteration to the next. I suggest simply iterating the last digit in the string (e.g., change 1 to 2, or 2 to 3, etc....). Once you make certain all your Windows Phone apps have individualized values in this field, you should be able to deploy them all independently.
It could also be a missing image in the Package.appxmanifest. Check the visual assets tab in this file (VisualElements in XML) to see if there is some logo missing.
I changed package name in Package.appxmanifest file. So I had to Uninstall app and Re Installation helped me.
I'm trying to move an app created in flash professional cs6 to my 7" RCA tablet (serial number:RCT6378W2), but when I try to publish it, flash doesn't register the device as connected at all. The device is connected to my PC running windows 7 64 bit via USB to mini-USB. The device shows up in the computer panel as if it is connected. I have USB debugging activated on the device, I have the android SDK as well just to be sure I'm running the appropriate drivers to make up for the lack of drivers built into the RCA tablets for USB. The device runs android version 4.2.2 with jelly bean. I've already created the APK file through FLASH from the SWF. So, after all that I've been trying to bypass publishing and simply use the AIR SDK to download the app to the device using ADT commands and arguments.
adt -installApp -platform android -device RCT6378W2 -package C:\users\me\Desktop\FILE.apk
the command line returns either one of the following errors:
invalid argument
invalid device
To be clear, flash won't recognize the device when publishing. I've entered all of the appropriate info in the publishing settings, created a certificate, I even have the APK file ready to go saved on my desktop.
Does anyone have any experience with this situation, is the tablet simply not able to handle what I'm asking? Am I approaching this the wrong way? Any thoughts at all are appreciated.
Running adb with the 'devices' keyword and NOT getting any devices listed should tell you that you DON'T have a suitable USB driver installed.
Try the 'universal' driver found here:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
Restart your computer for good luck and then run adb again. Make sure that your tablet is connected to your PC and tat your cable is good. When your device is finally recognized by adb you can then see if you still have a publishing problem.