[quote='789258022, on-d-go, /thread/756183?answerId=789258022#789258022, /profile/on-d-go'] I would expect fileDescriptor1 to read from file1 [/quote] As I wrote in my original reply, Why would you expect that? The behaviour of file descriptors is well-defined. The behaviour you are seeing is allowed by the spec. What’s actually happening is that the kernel is allocating the same FD for the second open as for the first, which it can do because you closed the first one. So when you read, you read from the second file. What are you actually trying to achieve here? There may be other APIs that better match your requirements. If you really want to use file descriptors you need to understand them properly. You will be constantly surprised if you try to guess how you would expect them to behave.

[quote='756190021, vbovio, /thread/756190, /profile/vbovio'] I have seen posts of people mentioning that converting from Individual to Organization takes several weeks, while others have claimed that the Seller name remains the same even after the conversion [/quote] I did the individual -> company conversion. I forget how long it took; it may have been a week or two. I wasn’t in a hurry. But that was a few years ago, and right now I get the impression that Developer Program Support might be overworked. I’ve no idea about the name-not-changing issue, that sounds unlikely. I would suggest doing this rather than creating a second account and transferring the apps.

[quote='756183021, on-d-go, /thread/756183, /profile/on-d-go'] I would expect L13 to result in an error [/quote] Why? I don’t know what happens when all Apple’s extra layers are added on top, but the underlying behaviour of POSIX file descriptors is well-defined. If the file is deleted, the file descriptor remains valid and you can continue to read and write to what is now a “anonymous“ file. Only once you close the last open file descriptor for a file is it actually deleted.

whats the point of asking developers to hit consumption request API It is one input to their algorithm. It seems that presently they prefer to believe the user rather than you. That may change. Or not. this is a US based customer creating fraud/scam. When you’ve had maybe 100 such scammers, you should be able to see a pattern.

This issue happened with GPX files a few years ago. You might find something if you search the forum. At the time the only solution was to hope everyone would converge on the same UTI. I don’t know if something changed in iOS, but it has not been an issue for me personally recently, nor have any of my users complained for a while.

How can we stop this scam and bleeding? You can't. You need to ensure that you make enough profit from your honest customers to cover the expense of the scammers. My only other advice is to try to target demographics who are more likely to be honest, and/or less likely to know how to run a refund scam, in your advertising / promotions / etc.

Is it possible that if the productId has already created and deleted after ? And now we cannot created again with the samed productId ? It is true that you cannot re-use deleted product IDs.

glGetTexLevelParameter That doesn't seem to be available.

Try Address Sanitizer.

If I recall correctly, iOS supports ES 3.0 with a few extensions. So you may be able to get the 3.1 feature that you want by using ...EXT names. For example, separate_shader_objects. What feature do you want from 3.1 ?

Yes.

Hi Rick, I may have solved this! Try this: Add the UITextInteraction to your view. Iterate view.interactions. One of them will be a UITextSelectionDisplayInteraction that was added by the UITextInteraction. When you call becomeFirstResponder to present the keyboard, also set activated = true on the UITextSelectionDisplayInteraction. The cursor will appear! Note that has only been tested for about 30 seconds so far! You may be interested to know that I found this while trying to solve the related problem of how to avoid a "ghost" edit menu being left when I call resignFirstResponder; see https://developer.apple.com/forums/thread/751307 It may be worth not using UITextInteraction, and instead using UITextSelectionDisplayInteraction and UIEditMenuInteraction (etc?) directly, with your own logic to replace the glue provided by UITextInteraction.

You don't need to do anything in your app. You can either: Use AWS CloudFront, which will cache your files in regional edge locations. This works, provided that caching is effective i.e. you have sufficiently-frequent downloads that your content is in the cache. Use Route53 DNS with Geolocation or Geoproximity routing. (I've not done this. I have a feeling that it may be difficult to do this with HTTPS to S3.) You might also consider Cloudflare R2 as an alternative to S3 - it's cheaper.

Answering my own question.... When you add a UITextInteraction, a UIEditMenuInteraction gets added automatically. So it's possible to iterate through the view's interactions and find the menu interaction using isKindOfClass, and call dismissMenu on that. It's a bit of a hack, but I've done much worse and it seems to work.