Visual Studio Maui IOS

Same here. I guess we're not just using and reporting bugs for beta OS X 10.11 and iOS 9 this cycle but also beta ADC website.

Thanks so much for your response.I am not using a wildcard, but the full app ID. I've been trying to set signing for it. As well, the default settings seem to be for OSX and i've tried switching that to iOS and setting normal signing. Pretty confusing why it hasn't been working.Additionally, if i try to force a validation after my initial error, it tells me: Failed, the package does not contain an info.plist(The info.plist in the IAP is called a ContentInfo.plist) maybe that's a part of the issues?

Hi ! Yep you're missing it 😉 native apps are always linked to an parent iOS app for now. what's native is that watchkit code is now executed on watch. so it's the same way that before, Apple does the Job.what you have to do is call Webservices via the watch kit app for exemple. instead of calling the parent app.

Well, first you need to decide what you should put in different places. ie: watchos2 requires a different way of thinking. What are you calculating? If the inputs for the calculations come directly from Apple Watch, then it is much better that the extension runs on Apple Watch itself. If the inputs do NOT come directly from Apple Watch, you may think about doing calculations in parent app in background (or even on a server) and using WatchConnectivity to send them to Apple Watch from the parent iOS app.For instance, we (at Mouseaddict) track where the user goes inside of Disneyland when they are visiting. This type of data can be displayed on Apple Watch in a glance or watch app. (it does not now, but it could). This would be perfect for running on the parent app because the datam we are crunching does not come directly from Apple Watch itself - it is lat/lon and the phone provides that because Apple Watch doesn't have a GPS. Hence this should be crunched in the bkg on the parent iOS app and

You can still build a test your app on 2 and then submit using Xcode 6. I run beta iOS updates and then build production apps with the old Xcode - you don't need a device plugged in to do this. However you're risking missing bugs as your test OS doesn't match your build OS. As for switching between watchOS 1 and 2 - downgrades are not supported or reccomended.