We are in the process of submitting our app for the Mac App Store. I get the following email from Apple when submitting to the store:
Dear developer,
We have discovered one or more issues with your recent delivery for "YourApp". To process your delivery, the following issues must be corrected:
App sandbox not enabled - The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list. Refer to the App Sandbox page for more information on sandboxing your app.
• YourApp.app/Contents/MacOS/YourApp
Once these issues have been corrected, go to the Version Details page and click "Ready to Upload Binary." Continue through the submission process until the app status is "Waiting for Upload." You can then deliver the corrected binary.
Under Project Options->Mac OS X Application, I have:
Enable Entitlements – checked
Some iCloud stuff auto-filled out
Enable App Sandboxing – checked
Allow outgoing network connections – checked
Under Mac OS X Packaging – I manually selected an App Store distribution certificate as well.
To submit, I’ve been using Build->Archive and submitting from inside XCode. If I “validate” inside XCode, there are no errors.
Any ideas?
Sent this issue to Xamarin Support, and they figured it out.
They send me a new version of Xamarin to install that fixed the issue.
Should be an update soon if other people have this issue.
Related
I'm getting the following exception using AWSSDK v 3.5.1.58:
The encrypted store is not available. This may be due to use of a non-Windows operating system or Windows Nano Server, or the current user account may not have its profile loaded.
This is due to the application unable to use crypt32.dll. Now this is strange since the file is in System32 running on Server 2019 and IIS 10. There's no real documentation around this. I'm using ADFS auth. FederatedAWSCredentials
This works fine on local dev, but not once deployed.
The file generating the error can be found here: https://github.com/aws/aws-sdk-net/blob/133eddb00a3fbd2ab395e01c3d84ac9fe1ff38b2/sdk/src/Core/Amazon.Util/Internal/SettingsManager.cs on line 213
So the issue was in IIS.
I was running the Application Pool as the user that needs to be authenticated, which is correct. But you also need to set the following:
Application Pool -> Advanced Settings -> Process Model -> Load User Profile = True
RDP to your server
and follow the steps in the image
I wrote a UWP program and I used Restricted capability
broadFileSystemAccess
When I published this application I obtained permission from Microsoft, and its now in the Microsoft Store.
But when I tried to install it, it got an error:
My computer: Windows 10 1809
I have tried googling this, and writing to Microsoft, both without finding a positive result.
First, make sure the problem is actually only with your app by trying to install some other app if that will work.
If this happens only with your app, you should definitely contact Windows developer support for this issue. Select Contact us tab, then Windows 10 UWP app development and submit your incident. They should be able to help. You can also post the problem on the publishing Forum for greater visibility.
I have a WPF application, which I have converted to a UWP application using the DesktopAppConverter for the purposes of running it in Assigned Access mode - the converted app works when run in non-assigned access mode - can be installed and functions properly.
However, when I set it up to be used as an assigned access application and log in with the account for assigned access, the screen keeps flashing (blue screen with loading dots, followed by a white screen, and repeat) for a period of time, resulting in the 0x80270254 error displayed.
Also after checking the Windows Event Logs I get two error messages in succession:
The application MyAppName is not registered for the Windows.Launch contract or is not installed.
ActivateApplicationForContractByAppIdAsUserWithHost of the app MyAppName for the Windows.Launch contract failed with This app does not support the contract specified or is not installed.
I've been trying to debug the app, including making changes to the AppxManifest.xml file and rebuilding the .appx package, making changes to the properties of the original WPF app that it came from and making changes to the Assigned Access user account's environment with little to no success.
Any tips for the resolution of the issue would be much appreciated.
Thank you for reporting this issue.
We got the confirmation that the Assigned Access mode doesn’t support Win32 apps yet, including Win32 apps converted with the Desktop Converter.
It is a known issue in RS1 which can pick Converted app in setting UI. We have a planned fix for this in RS2 but do not guarantee it will be delivered soon.
Please see this article for how to use Shell Launcher to config a kiosk device that runs a Classic Windows application as the user interface: https://technet.microsoft.com/en-us/itpro/windows/manage/set-up-a-kiosk-for-windows-10-for-desktop-editions
I have developed a Windows phone 8.1 app. Now I want to distribute it to others.
I have done Create App Packages in Visual Studio, and it passed all the certification tests. So I have the .appx file, but I am not able to install it in other Windows phones.
Its showing this error:
Can't install this company app: There is a problem with this company app. Contact your company's support person for help.
I have googled and found out that there is two ways of distributing the app:
1) Mobile Device Management Tool,
2) Side-Loading
and without having an enterprise-signing certificate from Symantec it is not possible to distribute the app.
Another option is to upload the app to the store, but I don't want to do it at this moment.
So is there any way to install the app in other windows phone?
In a simple way? I don't want any certificates. I just simply want to install the app in my friends phone. Like we can create and install .exe files easily.
There are a few ways to achieve this without getting the certificate required for sideloading.
Beta
First of all - you ask for the simplest way to distribute an app.
I assume that there might be updates in the future (and if only to fix this annoying little bug that might find or whatever). Then submitting it to the store as Beta app is really something you should consider; it won't be visible - it won't be accessible to anyone whom you haven't authorised to use the app. The certification process in Beta is quite fast, as it is merely a sanity check.
Regarding the cost of the dev account: it is quite cheap (https://msdn.microsoft.com/en-us/library/windows/apps/jj863494.aspx) and can even be free, for students and startups through the respective programs (DreamSpark, BizSpark). Also: no recurring fees, even if you're not a student anymore.
But the true benefit is that all you need to do is give the authorised testers the link to your app once it is published and then all the updates are handled through the store. No messy package distribution to the individual people, no notifications - testers will get the updates like for every other app. Long term, that would save you a lot of time and the testers a lot of hassle in preparing their device for being able to play your app, they do not need to developer unlock their phones.
Without Beta submission
If you want to just send them the app package,
they must (also) have a Microsoft account. If I recall correctly, they can have one developer unlocked device even without the dev registration (http://dev.windows.com/en-us/join)
they need the Windows Phone SDK, which comes as part of Visual Studio, which installs the required tools
connect their phone to the computer
to developer unlock their device, they have to run a tool called "Windows Phone Developer Registration" and sign in with their Microsoft account
to deploy the app, use the tool called "Application Deployment".
Everytime an update is distributed, they simply need to use the "Application Deployment" tool.
or use the command line :D
Unless your friend's phone is developer unlocked, you have to submit it to the app store.
Background: ClickOnce app that is bundled with the web server of an embedded device. Customers access the web interface, like you would access your router's configuration pages, and hit a button there to launch the ClickOnce app.
Problem: One customer claims he is getting signing error "Cannot continue. The application is improperly formatted. Contact the application publisher for assistance." And in the details, "Your Web browser settings do not allow you to run unsigned applications." This happens before ClickOnce even gets to the part where it downloads the app. Just click the "launch" button and the error is immediately thrown. Customer is running Windows XP and IE8.
The application and deployment manifests are both signed with our VeriSign Class 3 Code Signing certificate. I have check and retested a dozen times with different IE settings, and every time it downloads the application, successfully verifies, and launches. We've had him reflash his device and same thing. No one else has this problem, just him, so I can only conclude that there is nothing wrong with the manifests or their signatures.
His IT department is freakish about security so I strongly suspect that he has some IE settings interfering with ClickOnce, either trying to enforce stricter signing requirements, or blocking it altogether. What could be causing this? Are there some group policies somewhere that are maybe shutting him down?
Try clearing the browser cache.
Go to Internet Options -> Advanced, then click Reset...
For me worked check in Internet Options -> Advanced -> "Allow Software to run or install even if the signature is invalid"