I have a Xamarin iOS app that I am trying to distribute in the App Center. It will send out an email and install fine, but when you run it, you get the error
MyApp.iOS Wants to use "appcenter.ms" to sign in.
I have the option of cancelling or continuing. I hit continue and it signs in and says In-App Updates are enabled. It then returns to my app with the message:
In-App updates disabled.
This release was either side-loaded or downloaded using a browser in private mode.
I can either Ignore or Reinstall app. Ignore lets the app work, but it no longer checks for updates. If I Reinstall app, it opens App Center and I can install it, then it starts back at the beginning. It is using Safari to do the original install. I assume that when it does the Reinstall app from within my app, it is using a Safari based browser. Nothing is in private mode as far as I can tell. My startup code for App Center is
Distribute.UpdateTrack = UpdateTrack.Private;
Distribute.DisableAutomaticCheckForUpdate();
AppCenter.Start("11111111-2222-3333-4444-555555555555",
typeof(Analytics), typeof(Crashes), typeof(Distribute));
In my main view, I have the code
public override void ViewDidLoad()
{
base.ViewDidLoad();
Distribute.CheckForUpdate();
}
In my Info.plist I have
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleURLSchemes</key>
<array>
<string>appcenter-11111111-2222-3333-4444-555555555555</string>
</array>
</dict>
</array>
Cookies are not disabled that I can tell. I have searched high and low and can't find anything like this. The only similar issue seemed to be someone messed up the Info.plist. Can anyone help?
OK, I finally figured this out. When I was testing the distribution of my app from the App Center, rather than spam the whole group until it worked, I just distributed it to myself. This is what caused the problem. What I had to do was to create another distribution group and only have myself in it. Automatic updates started working once I did this. The point being is that if you don't distribute it to a group, then it thinks it's side-loaded.
Related
I am trying to save an extension that Apple is killing with their move to safari app extensions.
I am running OSX beta 10.15 and the latest Xcode beta.
There is a new API contentBlocker(withIdentifier:blockedResourcesWith:on:)
But as with other related updates in this space the documentation is lacking.
Is there anyone out there that knows how to get that to function?
Or is able to point me in the right direction?
Specifically, how does this work and how to get it to work?
Do I need to implement my own content blocker?
If so, then how does the communication between the content blocker and the safari app extension work / what needs to be configured to make that communication work?
Would be nice to have this tested before 10.15 actually goes live...
You'll need to first create a new target in the project for your Content Blocker. Then, in the info.plist for your Safari extension, under the NSExtension dictionary, add:
<key>SFSafariAssociatedContentBlockers</key>
<array>
<string>BUNDLE ID FOR YOUR CONTENT BLOCKER</string>
</array>
You can then add the contentBlocker() method to your SafariExtensionHandler class.
I've updated XCode7 and like everyone, i have to amend a part of my code to be compliant with Swift2.
But i have a problem, when i m testing the app on the simulator i have no problem. But when i m trying directly on my real device (Iphone 5S IOS9), a black screen displays just with the level of the battery.
I have tried during 3 days to find something on stackoverflow, but nothing seems working.
This topic seems to be the same problem, but doen't work actually. IOS 7 launch image, displaying black screen on device ONLY
I' ve followed the topic iOS 9 Black Launch Screen but it doesn't bring any correct solution
Any idea, or help will be appreciated.
Its worked for me:
You can solve this problem using following steps :
First select root level of project and then go in General tab and Find that below blocks.
By default, in "Launch images Source" it shows "Use assets catalogs", click on it
It will ask you to "Migrate launch images to an asset catalog", simply click on "migrate".
Now, In same block in "Launch Screen file", remove default launch screen xib or storyboard. because we don't need to specify it. Just put blank on there.
Now it shows, "Brand Assets" in *launch Images Source", just click on right side arrow of it and set all your app launch screen assets with specific naming scheme.
Press "alt + cmd + shift + k". It will clean build folder of your application.
Now, build and run your app in device.
When your app connects to an Webserver or to a domain with localhost or non https means http , than post below into your info.plist:
<key>NSAppTransportSecurity</key>
<dict>
<key>NSExceptionDomains</key>
<dict>
<key>127.0.0.1</key>
<dict>
<key>NSExceptionAllowsInsecureHTTPLoads</key>
<true/>
</dict>
<key>localhost</key>
<dict>
<key>NSExceptionAllowsInsecureHTTPLoads</key>
<true/>
</dict>
</dict>
</dict>
This let the app make an exception to use Urls without SSL / https.
I've embeded youtube videos in ios 8 many times using the following code (I intentionally replace the video code with ----). After upgrading to ios 9, the video no longer plays (go to a YouTube Help page title "Video player error message".
Does anyone know what changed in ios 9 and how to fix this?
NSString *EmbedCode = #"<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/-------\" frameborder=\"0\" allowfullscreen></iframe>";
[[self webviewer] loadHTMLString:EmbedCode baseURL:nil];
In iOS9 it is important to switch everything to HTTPS.
So I'm facing the same problems like you. Some videos are playing, some videos are not playing.
See Apple’s App Transport Security Technote for full details
(Source: WWDC 2015 session 703, “Privacy and Your App”, 30:18)
You can also ignore all app transport security restrictions with a single key:
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
</dict>
With adding the key everything works. But I think this is only a temporary solution. You don't know when apple starts rejecting this.
I also filed an issue at Google.
Had the same issue, but in the last few days, it has started to work on iOS 9 with no security exemptions. I think Google got their servers up to the required security levels.
XPC communication works fine when I launch the targets from my Xcode. But, when I manually launch the service and client apps by double clicking them on the icons, the connection invalidation message shows up.Whay do they work fine inside xcode and not from outside ?.What magic is Xcode doing here to make the communication work.
For all folks, who met the same problem using xpc_connection_create_mach_service: XPC works through a lot of launchd stuff; when we are debugging the app in xCode, it mediates the app and launchd connection, but without xCode we need to do it ourselves.
To get this alive, the one should start it through launchd using the launch plist file.
There is an example of such plist here, but it's not enough.
The trick is the MachServices key, which looks like:
<key>MachServices</key>
<dict>
<key>com.server.bundle-id</key>
<true/>
</dict>
This is the way we are creating the mach service, so I guess our XPC connection may have some mach port below it.
I have made a Windows Phone app (for WP7.1) that uses BackgroundAudio for streaming, nothing too complicated. It was approved and made available for download in the store. However it no longer works, i.e. the app worked in debug+release when run from VS2012, and I assume the .xap I uploaded worked since microsoft approved it (they rejected it once and I was able to reproduce and fix the bugs they reported).
When downloaded the app simply bails on load on WP8 (lumia 820) i.e. flips back to the tiles immediately.
On WP7 (lumia 800) but the playbutton ignores input, however it downloads and displays the playlist, so some kind of functionality+network connection works.
I have tried the basics: installing using the application-deployment tool (app working), running the "Store Test Kit" which reports some slowdowns in the UI animations, but nothing serious (I hope).
Any ideas how to reproduce ".xap approved and downloaded from store but not working" or getting debug info from the phone without VS? Or any other things i can try out?
Every time your app crashes it will be logged and reported on your Windows Phone Dev Center Account. Just go in there and export the details to excel. Get the stack trace and put it in here. Maybe we can help.
The very first thing i can tell you is the opening page has some exceptions and that too it doesn't go well with some phones. Seriously there are concerns when a wp7 app is ported on wp8 device and vice-verse. To the extent of my knowledge there might be some binding issues. make sure you got the binding class to be public. And just as #AMR mentioned go the dev center and export the stacktrace. Try resolving them. Moreover if an app get certifies, it doesn't mean it is completely error free. The tests are limited to very coomon errors only.