when [[alloc] initWithNibName] returned, it was not guaranteed that those nibs would be loaded I do think it is loaded when initWithNibName returns. As for avoiding an extra view, I do not see this as a problem. There are so many objects allocated by the system, that even if you have hundreds of view, just an extra view each time will not make a difference. There are probably many other places in code more important top focus on if you need to optimize. In anycase, good to read it works. You should close the thread now.

Are you sure key is a valid SecKey ? A SecKey instance that represents a key that is stored in a keychain can be safely cast to a SecKeychainItem for manipulation as a keychain item. On the other hand, if the key is not stored in a keychain, casting the object to a SecKeychainItem and passing it to Keychain Services functions returns errors. Do you get a printed error ? If yes, which ? Do you get error when calling SecKeyVerifySignature ?

Did you try to do what you were asked to ? What happens then ?

My question was whether SecKeyVerifySignature did return true ?

What have you changed on your side ? update Xcode ? modified project ? Is the same occurring for every project ? Are you sure the error points to what you showed ? May be the line with dict dict keyCFBundleDevelopmentRegion/key stringen/string Could you post more of the info plist ?

Try changing line 12 by adding id:                 ForEach(group.ongoingItems, id:\.self) { item in

Could you show more complete code, so that we can understand how the pieces tie together and try to reproduce ?

Yes, it is annoying. That's not the case on SO… But a problem is that very few close the thread once they've got the answer they needed. May be a reason. I would advise you to file a bug (please report FB ref) and then… to close the thread.

So could you add complete code replicating the problem, so that we can test ?

I would first do an option-Clean Build Folder and see what happens. Could you tell what is the longest task reported in the log (could you copy the complete log ?)

If code works OK, that's the most important. From time to time, Xcode sends messages which should be ignored (they may be for debug use). Annoying but no real concern. However, you'd better file a bug report, in case.

The perfect filter does not exist. Even big companies have been compromised (I read that Xcode itself had been compromised in China 5 or 6 years ago). What I would do (and try to do myself): be cautious on the apps you download organise rolling backup of your important stuff (at least on 2 different physical support, where you alternate successive backups) apply a very strict discipline never to open a mail attachement if you are not 120% sure it is OK update OS to the last available security patches if one day you fear a machine has been compromised, immediately disconnect from the network and quarantine.

I have Downloaded update thrice time Downloaded what ?

That may be a beta problem. Did you file a bug report ? Then wait for 11.4 release and just don't shut down, just close the Mac screen to sleep (ctrl-shift-Power buttkeyn).

Did you try yo use the Debug View Hierarchy in Xcode during execution, to see exactly what the hierarchy of views is ? To access the tool, it is the 7th icon - shaped as a vertical rect with 2 smaller rects on its sides - from the left on the frame above the console) You may find an intermediary view that you have to make transparent. I tried rapidly, and found several layers (one is dropshadowview)