Post not yet marked as solved
Just for your happiness: adding my similar issue but with a different kit (StoreKit) and in lldb.
(lldb) po product
error: expression failed to parse:
error: Couldn't lookup symbols:
type metadata accessor for StoreKit.Product
(lldb) po product.subscription
error: expression failed to parse:
error: Couldn't lookup symbols:
StoreKit.Product.subscription.getter : Swift.Optional<StoreKit.Product.SubscriptionInfo>
(lldb) po product.subscription?.promotionalOffers
error: expression failed to parse:
error: Couldn't lookup symbols:
StoreKit.Product.subscription.getter : Swift.Optional<StoreKit.Product.SubscriptionInfo>
Post not yet marked as solved
Issue is still there, with Xcode 12.4 and macOS 11.3. It's *Very* annoying.
But what is even more annoying, is the behaviour of the Filter of the Project panel. Our project is really big, has many files, all ordered in groups. And to find a file/class, I often use the Filter option (basically there is no other find option).
With the new Xcode, I have two issue with this:
Often the Navigator panel suddenly can't resize anymore. Even though just seconds before, it would resize fine.
If I do a Filter, then select my file, and then clear the filter, the previous state of the panel is restored, and my file selection is undone, bringing me back to square one.
Previously, if I would select a file or a folder, with the panel filtered, and then remove the filter, my file selection would be kept, and all of it's 'superfolders' would be disclosed as well.
So, previously, I could filter for a file that I know was part of a Group with more files. Then select the file. Remove the filter. And then get to see all the other files belonging to the group/folder of the file I selected. Extremely useful when you have a big project and keep files that belong together, together in one group.
This one change, has significantly impacted my effectiveness in debugging. Because now suddenly, I basically can't search for files in the Navigation panel anymore and have to avert my attention to browsing through the navigation panel to get to the files I want to inspect.
Post not yet marked as solved
I am seeing the same issue. Once in a while, my app does not export e.g. blood pressure correlations. Even though in the same run I also export heart rate samples, which are successful.The strange thing though, is that on the Apple Health dashboard, I DO see my measurement. And I also see it in the chart! But when I go to Show All Data, the measurement is not shown. And if I look in Data Sources & Access, my app is listed as 'Inactive'.Deleting and reinstalling the app helps to often solve it. But now I have my app exporting blood pressure fine, but still my app is listed as 'inactive'!I recently rewrote the HeatlhKit export code of my app, in the hopes of (amongst other) fixing this issue. But the new code does the same as the old code, with respect to inactive data source.I have no clue what's going on. But I think there is some serious bug in the Health App. Anyone can shed some more light on this?
Post not yet marked as solved
And I am having the same issue as well. I call SecItemCopyMatching, and once in a while I get no dialog, and my UI is frozen. If I wait long enough, I do get to see a dialog. Sometimes after 3 or 4 seconds, but sometimes after 20-30 seconds. But always, if I touch the sensor, suddenly the popup pops up and login is successful.I have a feeling that it's simply a UI issue that the popup is not being shown for a while. But I can't verify it, because it all happens inside SecItemCopyMatching.I am actually using the SimpleKeychain pod. But that's not much more than a thin wrapper around the Sec calls.It also looks that if I have switched of connectivity, I can reproduce the issue easier. But still not 100%. Maybe 2 out of every 10 tries.My app is not doing anything concurrently when SecItemCopyMatching hangs. And SecItemCopyMatching is called on the main thread (in fact, I dispatch_async(dispatch_get_main_queue(),... the function that does the SecItemCopyMatching, and only continue when it returns.Any clues?
Post not yet marked as solved
The documentation says this:"If the myAnchor property is set to
nil, the query returns all the step count data currently available in the HealthKit store. On subsequent runs, the code uses the anchor returned by the previous query. These queries return only the step count samples that have been saved or deleted since the previous run."
So, am I wrong in assuming that if I make an initial query with the anchor set to nil, and a limit of 50, I would get the first 50 samples available in the HealthKit store? And if I use the returned anchor, and do a next query with a limit of 50, I would get the next 50 samples available in the HealthKit store?I get the feeling that I'm only getting all the data currently available in the HealthKit store if I set the limit to HKObjectQueryNoLimit. If I set the limit to anything else, it seems like I do get SOME of the data, but never ALL of the data. In fact, it seems like the AnchoredQuery with a limit works more like an update query with a limited number of returned items, than something that returns ALL the data.
The documentation doesn't mention anything about this.
