when I delete data, the size of the app remains unchanged and sometimes increases, AFAIK, deleting data does not mean that you purge the space and compact the database. You should probably have to recreate the database completely, just keeping existing records. In any case, does this cause you problem or is this for understanding ? Note: may be interested in reading this: https://stackoverflow.com/questions/64677236/how-to-check-the-size-of-coredata-in-swift

Why do you expect A to be cancelled ? A and B run each in their thread, no one expecting from the other, just c is awaiting and throws error, but A remains untouched.

Thanks for the clarification.

Whenever I click save it prints 1 more object then I already have regardless of how many favourites there are. Isn't it what you expect to have one more object ? I don't really understand your comment here. if I have 53704 saved objects then after I click save I have 53705 it seems to always be over 40000. What is the real number of objects you should have ?

Hiding views is the easiest to implement. The views would all be active all the time, just hidden. What's the problem here ? But there are many other solutions, it depends what you want precisely. You could use PageView and swipe between them: https://developer.apple.com/documentation/appkit/nspagecontroller create collectionView, with cell of exact size of the full view : h t t p s : / / w w w.appcoda.com/macos-programming-collection-view/ use splitView to have the list of pages in Master on the left and content on the detailView on the right. Once again, it depends on what user experience you want to provide.

Well, I will just recreate a new pdf, picking pages in the order I need.

Finally fixed it: I added a "rotation" along y axis, and now get the correct result: // -->> REMOVED THIS. let m = page.getDrawingTransform(.mediaBox, rect: mediaBox, rotate: 0, preserveAspectRatio: true) writeContext!.translateBy(x: 0, y: pageRect.size.height) writeContext!.scaleBy(x: 1, y: -1) writeContext!.translateBy(x: pageRect.size.width, y: 0) // <<<--- ADDED These 2 lines writeContext!.scaleBy(x: -1, y: 1) // -->> REMOVED THIS. writeContext!.concatenate(m) or equivalent : writeContext!.translateBy(x: pageRect.size.width y: pageRect.size.height) writeContext!.scaleBy(x: -1, y: -1)

It is still very difficult to understand your code, partly because naming of var is not explicit enough. What is prefArr ? How is it populated (if an array). When you save: you create a new instance saveFav then, I don't understand what you are doing in the loop. Is it just for displaying saveFav ? I do not see in save where you reference a newly created fav So the first questions: where and how do you create a new favorite how do you use it in save

At the end of FileHandle documentation page, you have the list of instance methods that you can use: func close() func offset() -> UInt64 func read(upToCount: Int) -> Data? func readToEnd() -> Data? func seek(toOffset: UInt64) func seekToEnd() -> UInt64 func synchronize() func truncate(atOffset: UInt64) func write(contentsOf: T)

Show code please.

Rationale is usually the limited screen real estate. In SE, is it a Floating bar ?

AFAIU, no, it is not turned off, as it is receiver only. But maps are not updated, because you request the map area to a server, then need to transmit the request and thus use emitter. Is it the thread you were looking for ? https://discussions.apple.com/thread/8048257

There would also be a leaderboard and if you drank a certain amount of drinks you would get a discount on the next one. My understanding is that the app would incite to drinking. And app will likely be rejected under 1.4.3 and may be 1.4.5 as well. I would also like to know if there is a support number that I can use to contact an App Store employee/reviewer so that he/she can clarify these questions before having to submit the app for review. No there is not. And no way to have upfront information on the review beyond the guidelines. You have to submit and wait for the review.

If you are running your app only on iOS 14.1 What do you mean ? You do not get the problem on other versions of iOS ? Did you change the content direction as well ? navigationController.view.semanticContentAttribute = .forceRightToLeft self.navigationController?.navigationBar.semanticContentAttribute = .forceRightToLeft May read this: https://stackoverflow.com/questions/68019133/move-the-navigation-item-title-to-the-right-side-of-your-navigation-bar-in-swift

Could you NSLog to see exactly what you have for valueLabel and desiredLabel?