“A Summary of the WWDC25 Group Lab”

App store apps are per Apple ID and in some cases Family ID groups. You cannot restrict it to one machine.If this is an important issue for your app, the app store is not the place for your application.

Hmm, I have a similar issue I cannot get rid of even when setting opti-level to -01. This problem gets triggered pretty early in my app's code rendering ASAN rather useless... bummer.===================================================================6125==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x00011153a191 at pc 0x000100361830 bp 0x000114f82d20 sp 0x000114f824b0READ of size 4 at 0x00011153a191 thread T55 #0 0x10036182f in wrap_memcpy (/private/var/mobile/Containers/Bundle/Application/3CFC02D5-E600-4990-B8E0-BD41E16A710D/Lokate.app/Frameworks/libclang_rt.asan_ios_dynamic.dylib+0x3582f) #1 0x180f0b3a3 in agxuEmitRenderPipelineState (/System/Library/Extensions/AGXGLDriver.bundle/AGXGLDriver+0x373a3) #2 0x180f05c6f in glrAGXRenderVertexArray(GLDContextRec*, unsigned int, unsigned int, int, int, unsigned int, void const*, int, void const*) (/System/Library/Extensions/AGXGLDriver.bundle/AGXGLDriver+0x31c6f) #3 0x1864e8e57 in <redacted> (/System/Library/Frameworks/OpenGLES.framework/GLEngin

*** = l s d (without spaces, the forums want to convert to *** if i don't put in the spaces). It's LaunchServicesDaemon, right? it's crashing every 5 secondsProcess: *** [859]Path: /usr/libexec/***Identifier: ***Version: 728.2Code Type: X86-64 (Native)Parent Process: launchd [1]Responsible: *** [859]User ID: 0Date/Time: 2015-09-02 11:59:54.221 -0400OS Version: Mac OS X 10.11 (15A263e)Report Version: 11Anonymous UUID: 98FBD7C6-A1F5-E174-F66F-39ECB5EA836CSleep/Wake UUID: F34186CE-391C-4AE0-B065-7872862CF447Time Awake Since Boot: 830 secondsTime Since Wake: 390 secondsCrashed Thread: 2 Dispatch queue: com.apple.***.databaseException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x000000010f278980Exception Note: EXC_CORPSE_NOTIFYVM Regions Near 0x10f278980: Dispatch continuations 000000010e800000-000000010f000000 [ 8192K] rw-/rwx SM=PRV--> mapped file 0000000110280000-0000000111b90000 [ 25.1M] r--/r-x SM=ALIThread 0:: Dispatch queue: com.apple.main-thread0 libsystem_kernel.dylib 0x0000

I think that's a bit like saying: Biology is important, but it fails for simple things like describing green plants. It's not by chance that biology gets really ugly in these areas and needs sick stuff like photosynthesis.Yes, managing the GUI and state of a simple app is easy no matter what tools/concepts you use. But managing sufficiently complex GUIs together with some database state and so on, is not simple things, but it can be made simpler by using good tools/concepts. And it's not by chance that many/(most?) large such systems (eg Facebook et al) tend to use some form of functional programming (inspired) approaches for managing exactly these things (using eg React or some other form of futures, streams, signals, reactive / flow based things). This, and the fact that mainstream programming languages adds lambdas, map, filter, etc is not just some short lived craze, it's because they are useful, as is the concepts of various classic data structures, and OOP, FP, delegates, and monads.Monads are not some

From what I understand you need an Asset Catalogue with the WKExtension as it's target and create a group named Complication inside, however I'm not seeing anything in the dropdow for ComplicationGroup. Did you get this to work?

HI Jmml97,I'm also facing the same issue in ios 9 (Beta 5). Have you got any solution for it?????Basically universal group images were showing but they are not perfectly fit for iPad Air and iPhone 6. So universal will not work for me

Might be worth forcing Messages to rebuild it's container (this won't affect your messages). To confirm that this may work, see if Messages is starting up in a temporary new account. Create a temporary new admin account from System Preferences > Users & Groups > Open Padlock > + button. Log into the new account and test...

In XCode 7 beta 6 I didn't get this error. But I was required to implement `init?(coder aDecoder: NSCoder)` even though the initializer exists in the superclass. This code compiles (and you could alternatively also call `super.init(coder: aDecoder)` if you have a default for `thing`):import UIKit class MyViewController: UITableViewController { var thing: Int init(thing: Int) { self.thing = thing super.init(style: .Grouped) } required init?(coder aDecoder: NSCoder) { fatalError() } }For XCode 6, what you report seems to be a known problem with a discussion and some proposed solutions here:http://stackoverflow.com/questions/25139494/how-to-subclass-uitableviewcontroller-in-swift(check out the code of the first answer)

Maybe because I'm building for iOS 8 and running 8.4 iPad? Did you test on 9.0?That's it. I could reproduce your issue with iOS 8.4 sim. Sorry for having missed such basic settings.Another work around is to make your init(thing:) a convenience initializer. (You need to make `thing` as Thing! in this case as well.)class MyViewController: UITableViewController { var thing: Thing! convenience init(thing: Thing) { self.init(style: .Grouped) self.thing = thing } //No designated init cannot appear... }While adding only convenience initializers, your class can inherit all designated initializers including init(nibName:bundle:) .

For clarity, you worte:validation worked large majority of users, but it seems there's always a small group of users that have problems. Some users are original buyers of the app, while others are IAP users. Do you mean that some users WHO DON'T GET VALIDATION are original buyers of the app while other users WHO DON'T GET VALIDATION are IAP users? Or is the problem just with one or the other type?I always ask users to delete app from the device and download it again from the AppStore, which forces the receipt refresh, and that works well for many, but not all. Are you here referring to needing to refresh the receipt even if the app is deleted and downloaded again? You should expect that based on exactly how the app is downloaded into the device - there are a few different methods. But is your problem that you don't refresh the receipt and tehrefore get no validation? Or do you refresh the receipt and then fail validation.