How to delete an unpackaged app from HoloLens 2 - hololens

I'm having trouble deleting an app from HL2 which was deployed directly from Visual Studio.
I want to delete it because i want to deploy a packaged version through Device Portal.
Obviously it gives an error message:
Failure reason: Another user has already installed an unpackaged
version of this app. The current user cannot replace this with a
packaged version. The conflicting package is AppName and it was
published by CN=CompanyName. Failure text: The provided package is
already installed, and reinstallation of the package was blocked.
Check the AppXDeployment-Server event log for details. (0x80073cfb)
So i have tried to delete it on Device Portal, but there is an error message again:
Failed to uninstall package AppName_1.0.0.0_arm64__...
I have tried to delete it directly from the HoloLens, the app icon disappers from the HoloLens, but the application is still in the Installed Apps list. (And i cannot deploy the packaged version)
Is there a way to force delete an application?
HoloLens2 OS version: 20348.1518.arm64fre.fe_release_svc_sydney_rel_prod.220906-1328
UPDATE:
On the Device Portal, when i want to remove the app i get response on DELETE api/app/packagemanager/package?package=AppName... with code 500 and body
{"Code" : -2147009295, "CodeText" : "Package was not found.\r\n", "Reason" : "Windows cannot remove AppName_1.0.0.0_arm64__... because the current user does not have that package installed. Use Get-AppxPackage to see the list of packages installed.", "Success" : false}

Related

Visual Studio 2022 fails to load nuget packages from custom package repository

I'm using Visual Studio 2022 Update 17.3.3
I have some nuget packages in a custom store, maintained by my company. Accessing those packages used to work in the past. The way we set it up is generate a PAT on Azure ADO, and then use nuget to register them as package sources like this:
nuget.exe sources add -name mypackagerepo -password myPAT -username username#ourdomain.com -source https://pkgs.dev.azure.com/mycompany/_packaging/mypackagerepo/nuget/v3/index.json
A few days ago, Nuget Package Manager started to fail with the error
[mypackagerepo] Unable to load the service index for source https://mycompany.pkgs.visualstudio.com/_packaging/mypackagerepo/nuget/v3/index.json.
Response status code does not indicate success: 401 (Unauthorized).
If I open that link in a browser, I get HTTP 200 and a valid JSON response.
One series of steps to produce the error is
In VS / Tools / Nuget Package Manager / Manage Nuget Packages for Solution
In Package source, select the custom package source mypackagerepo
In the Browse tab, hit Refresh
VS displayes "Error occured"
Hit "Show errors in output"
The above error message is visible
I tried a bunch of things suggested by others
restarted VS
restarted my PC
removed my %appdata%/Roaming/Nuget/nuget.config file
created a new PAT and recreated the package source registrations
cleaned up (removed all VS related entries from) my credential cache
repaired then reinstalled VS
Any ideas how to fix it?

Android Studio does not install app after using the Internal Test Track version

I've been working on my app for a while now and recently uploaded it to the Google Play Console's Internal Test Track. I installed my app via Google Play Store and it worked fine.
But if I now try to install an updated debug version via Android Studio directly it just launches my main activity without installing the changed app.
What I've tried:
Uninstalling app and running in via AS: "Error: Activity class {...} does not exist."
Restarting phone
Restarting AS
Reconnecting phone
Uninstalling app via AS (gradlew uA)
Uninstalling app via app manager
Invalidating AS cache
Cleaning / rebuilding project
Disabling Skip installation if APK has not changed in Run Configurations -> Miscellaneous
Increasing version number
What may cause it:
The Internal Test Track version is signed, but the key is kept by Google
The app is not selected as 'App to debug', but the dialog to choose one, does not offer it
How can I install my unreleased version via Android Studio directly again?
Thanks in advance. -Minding
QUICKFIX
The "Gradle Aware" task was missing for some reason. To fix it "Run" > "Edit configurations" > "+" > "Gradle-aware Make" > "OK" (leave the field empty) and restart.
The Android Studio team is still investigating why this happened.
Old answer / Workaround
Using the ADB to directly uninstall the release version and installing the debug version worked, but you have reinstall the app for every change! A better solution would still appreciated.
Build your project's debug APK
Enter the following into the terminal:
adb uninstall MY_PACKAGE_NAME
adb install -r ./mobile/build/outputs/apk/debug/mobile-debug.apk
If you get "adb" not found. use %LOCALAPPDATA%\Android\sdk\platform-tools\adb instead.
Select the app to be App to debug in the device's developer options.
Hope this help. -Minding

VS 2015 TACO - build broke on Xcode 8 / iOS 10

Here are the issues I encountered and fixed:
Code signing: downloaded the xcode8.js hook and added the following to build.json, per http://www.dpogue.ca/articles/cordova-xcode8.html:
"ios": {
"debug": {
"developmentTeam": "VZ4B5XSP9U"
},
"release": {
"developmentTeam": "VZ4B5XSP9U",
"codeSignIdentity": "iPhone Developer"
}
}
On my Mac, deleted the ~/.taco_home/node_modules/taco-remote-lib/2.2.1 and .../2.2.0 folders, per https://github.com/Microsoft/remotebuild/issues/5.
On my Mac, tried uninstalling and reinstalling remotebuild, and different versions of node and npm (0.12.9 and 4.6, and respective npm versions).
In Visual Studio, tried changing the targeted Cordova version: 6.3.1, 6.2, 6.1.1, and back to 5.4.1.
No matter what I do though, the build gets stuck either on extracted - Extracted app contents from uploaded build request, or building - Updating platform forever.
Earlier, when I tried opening the Xcode project in Xcode on the Mac, it successfully built and deployed the app to the device. I was then facing issues using WebRTC (using cordova-plugin-iosrtc) and it was giving me privacy violation exceptions. I tried adding the cordova-custom-config plugin and appropriate Cocoa keys (NSCameraUsageDescription and NSMicrophoneUsageDescription) per App crashes with __CRASHING_DUE_TO_PRIVACY_VIOLATION__ when trying to access contacts, and then it stopped working altogether.
Can anyone please advise what are the latest versions of all of the components I should be using to make it work again? Some sources advise to use Node 0.12.9 on the Mac, others 0.12.7; most people claim that with Cordova >= 5.3.3, any Node version should suffice, however using Node 4.6 didn't work either.
Thanks in advance for any help!
Update: After performing the brew update etc. as suggested by Jordan, the remote deploy works, but the build sets "Main interface" setting under project's General tab to "NSMainNibFile~ipad", which causes the app to crash on launch, until I open the project in Xcode and clear that field, then an incremental build creates a functioning app.
This is a known issue with Apache Cordova 6.3.1 and for the Visual Studio tools we've been working on a fix for this. To work around the issue for now, you'll need to perform the following steps:
Add a developmentTeam property to the ios build settings in your project's build.json file (an example is shown below).
Set the build.json file's codeSignIdentity property to the static value iPhone Developer.
Setup a before_compile hook in your project to copy the developmentTeam property into the project's platforms/ios/cordova/build.xcconfig file.
The project's build.json file should look something like the following:
{
"ios": {
"debug": {
"developmentTeam": "DEVELOPMENT_TEAM_NAME"
},
"release": {
"developmentTeam": "DEVELOPMENT_TEAM_NAME",
"codeSignIdentity": "iPhone Developer"
}
}
}
To simplify the process, Darryl Pogue published a sample hook that makes the required changes to the project's build.xconfig file based on the build.json example shown above. To use this hook, copy the sample xcode8.js file to your project's hooks folder, and then modify the project's config.xml to execute it before the compilation step using the following code:
<platform name="ios">
<hook type="before_compile" src="hooks/xcode8.js" />
</platform>
Creating a Distribution Build
At this point, the Cordova build process works, and you can run, test and debug your app. Unfortunately, the app isn't being signed with the correct development certificate needed for distribution. In order to sign them with a distribution certificate, you'll need to create an archive of the app by following the instructions found in: Uploading Your App to iTunes Connect.
iOS 10
Developers building Cordova applications for iOS 10 may encounter the following errors:
Http 404: Error mounting developer disk image
Http 500: No devices found to debug. Please ensure that a device is connected and awake and retry.
This is caused by the Mac development environment needing an update to several modules. To fix the issue, on Mac OS, open a terminal window and issue the following command:
brew update && brew upgrade libimobiledevice --HEAD && brew upgrade ios-webkit-debug-proxy ideviceinstaller

Cannot run the same App that used to run fine

I am creating universal Windows App using Visual Studio 2015. The App initially run fine but then something happen and App failed to been deployed. I just get following error.
I have tried uninstall the App, cleaning the bin and bld directories (even removing these), changing the package name (guid and display name) but nothing works. Any ideas on what cause this error and how to resolve it?
EDIT
Events Viewer is showing following entry.
ActivateApplicationForContractByAppIdAsUserWithHost of the app
0c2164b1-2ddd-4cef-9305-f061db235a23_nef0eajndckej!App for the
Windows.Launch contract failed with Install failed. Please contact
your software vendor..

Visual Studio 2012 Update 4 fails

Downloaded ISO and verified the hash. Installed Web Deploy 3.5 separately and Preperations.exe file is present in the "packages" directory..
After several tries, I even cleaned up "C:\ProgramData\Package Cache" directory, but nothing helps..
I'm going to uninstall Web Deploy 3.5 and try it again.. Any suggestions?
After uninstalling the Web Deploy 3.5, I got the error as shown in the screenshot.
Steps I've taken to fix this:
Downloaded Update 4 ISO from http://go.microsoft.com/fwlink/?LinkId=327544
Manually uninstalled Web Deploy 3.5
Ran VS2012 repair using the command-line (couldn't do it via Add/Remove Programs): vs_premium.exe /repair
Had to run the repair twice as it failed the first time
Ran Update 4 installer and it failed with following error:
[19A8:1FD0][2013-12-17T09:47:13]: Acquiring package: Preparation, payload: Preparation, copy from: C:\Users\Ostati\Desktop\Temp\VS2012.4\packages\Preparation.exe
[10C4:1550][2013-12-17T09:47:13]: Verified acquired payload: Preparation at path: C:\ProgramData\Package Cache.unverified\Preparation, moving to: C:\ProgramData\Package Cache\C6B63A9C9DFE6A89D63665FB41EFDD35689A78AD\packages\Preparation.exe.
[10C4:1550][2013-12-17T09:47:13]: Error 0x80070002: Failed to move verified file to complete payload path: C:\ProgramData\Package Cache\C6B63A9C9DFE6A89D63665FB41EFDD35689A78AD\packages\Preparation.exe
[10C4:1550][2013-12-17T09:47:13]: Error 0x80070002: Failed to cache payload: Preparation
[19A8:1FD0][2013-12-17T09:47:13]: MUX: Verify Failed. Retry acquiring, Retry Count: 1 of 3
Manually Copied C:\Users\Ostati\Desktop\Temp\VS2012.4\packages" to C:\ProgramData\Package
Cache\C6B63A9C9DFE6A89D63665FB41EFDD35689A78AD\"
Ran Update 4 again and it worked!**
I got the same error when installing update 4, and found the following error message in the log file.
[2B50:1FF0][2014-05-12T11:21:37]: MUX: ExecuteError: Package
(webdeploy_x64_en_usmsi_902) failed: Error Message Id: 30002
ErrorMessage: Installing some features of Microsoft Web Deploy 3.5 is
not supported when using Shared Configuration for IIS. Please disable
Shared Configuration before installing these features ("IIS 7.0
Deployment Handler", "IIS Manager UI Module").
It seems that you can't install the update while you've got a shared configuration enabled.
I fixed this by disabling my shared configuration, then repairing the update, then re-enabling the shared configuration.

Resources