I am trying to use AppCenter to distribute my app to iOS beta testers.
I have included the nuget packages for Microsoft.AppCenter and Microsoft.AppCenter.Distribute
I followed the developer.xamarin instructions for creating an IPA
An IPA did not appear in the Bin > iOS Device > Ad Hoc (or Release) folder as expected. An application (.exe) file was created.
This is most likely the area I need help on.
In AppCenter I selected Distribute and got to the Upload a Build screen, I could not find an IPA file on my computer.
when pressing the Where Can I Find my IPA file? link, I was transferred to https://openapi.appcenter.ms/, which I didn't understand how to use to find the file. Perhaps this link is incorrect or someone can tell me how to use these apis to find the file?
I have never connected my Windows Visual Studio Xamarin to a Mac. LivePlayer on an iPhone works beautifully. I was hoping to get to be able to distribute my app without using a physical Mac.
Thank you for any help. If you can point me towards other tutorials on setting up and using AppCenter to distribute to iPhone beta users, I would appreciate it.
To order generate an .ipa file for distribution a Mac needs to be involved in the build process.
If you do not have access to a Mac for local development and the application source code is located in a git repository hosted in GitHub, BitBucket, or Visual Studio Team Services, then you can link App Center to the git repository and configure App Center to perform the build for distribution purposes.
Related
I'm relatively new to coding so I have a website that I wanted to convert to an APK to upload to Google Play, so as I'm relatively new I used the program website2apk, all that went OK so when I went to upload it to Google Play I had this error
"
Unoptimised APK
Warning:
This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimising your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower installation success rates and take up storage on users' devices.
Resolution:
Use the Android App Bundle to automatically optimise for device configurations, or manage it yourself with multiple APKs."
So I installed Android Studio and tried importing the APK and the build is greyed out.
So decompiled it and tried importing the project, However I try to import it I get this (see the screenshot: http://prntscr.com/o2aoak).
So from there I'm clueless on what to do as I have tried both options and both don't seem to work.
Then when I tried create project from existing files it said I need to migrate to Gradle and I don't know how to do that.
I have a problem with a Windows 8.1 app that I want to deploy by sideloading.
I installed InstallShield premier to test it's feature, and generated an installation package that contains appx file and a test certificate file created by visual studio (associated in installshield project properties).
I need to enable app distribution in group policy settings to install.
After app correctly installs on system, i found it in start menu, but when i try to run the app, windows shows a popup that says "there is a problem with this app, contact administrator".
Target system is a Windows 8.1 Pro 32 bit PC.
Id there any other settings that I must enable on target system before install the app with InstallShield?
Thanks
There are multiple requirements for sideloading to work, documented on technet, which I've summarized here:
Activate the sideloading product key on the device OR join the device to an Active Directory domain (except for certain embedded devices which do not require either of these).
Enable the Allow all trusted applications to install Group Policy setting.
Since you don't mention it, I'm going to guess that your machine has neither the sideloading product key nor a domain membership (nor is it one of the special embedded cases), so that's where I'd start.
For more troubleshooting ideas, see some blogs like Sideloading Store Apps to Windows 8.1 Devices or How Do I Deploy a Windows 8 App to Another Device for Testing?
I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.
I've recently copied my visual studio 2010 website project from my windows 7 PC to a new PC running windows 8. That all went relatively smoothly. When I now publish or package the cloud project it only packages files that were originally on the windows 7 PC. Any files that I have created on the windows 8 PC are ignored. The solution builds fine and I can run and debug the project fine. Any ideas?
Not sure why that would be, but here's something to try: In Visual Studio Solution Explorer, right-click the solution and choose Clean Solution. Then try to package/publish again.
When you say files do you mean images/JavaScript?
What is the setting of the "Copy to Output Directory" ? for the files/content that is not making it...make sure it is NOT set to "Do not copy"
Are you using the new v1.8 of the SDK? (did you upgrade your project?)...this can happen if you are using an old SDK from a previous computer and then try to build stuff using a "fresh installation".
The issue was that somewhere along the way the cloud project got disassociated with the web project so wasn't actually updating the file list for publishing - it was just using the file list that had already been generated on my old PC.
The fix was to scrap the cloud project and start over with a new one, then add a new web role to it and then convert that web role into a web application project and then move my whole existing website into that...
We are trying to evaluate and eventually migrate to the windows azure cloud platform.
I am stumbling on the installation process...
I'm currently following this tutorial.
I can't get the Windows development Fabric interface working like on this picture.
When I install the app fabric sdk (downloaded here) I get no .exe program to simulate the cloud...
I installed Windows AppFabric which is not what I need (I think).
I keep on being directed on AppPlatformInstaller which do not install what I need but I'm sure is part of my solution.
You are downloading wrong SDK. For Windows Azure Cloud platform you must download and install Windows Azure SDK And Tools for Visual Studio.
Then you will have a folder %Program Files%\Windows Azure SDK\v1.5\bin. There will be devfabric and devstore folders, under which the local development Frabric and Development Storage executables will reside.
Then if you are targeting .NET based solutions, you will have new project templates in Visual Studio, and everything shall be running smoothly. On the other hand, if you are targeting open source solutions you might want to follow the like provided by Ben.
As for Windows AppFabric - yes, it is wrong in terms that it is not related to Windows Azure at all.
Let us know if you have any issues when downloading and installing latest Windows Azure SDK And Tools for Visual Studio
You may want to check out the docs available from the Microsoft Interoperability Team. They maintain an entire site dedicated to running PHP on Windows Azure
http://azurephp.interoperabilitybridges.com/articles/build-and-deploy-a-windows-azure-php-application
Basically to get it working just install the Windows Azure SDK and with Windows Azure SDK for PHP. Build your PHP application and then run the package command. Your PHP application will be rolled into a Windows Azure project and launched in the local dev fabric