“Account Locked”

Calling Objective-C directly from C is certainly possible and can simplify your codebase by eliminating intermediate layers. Additionally, using Grand Central Dispatch (GCD) to manage thread safety and dispatch tasks to Objective-C contexts is a sound approach. Below, I'll outline how you can achieve this, maintaining thread safety and leveraging GCD effectively. Direct Objective-C Function Call from C Assuming you have an Objective-C method you want to call directly from C, you can use the Objective-C runtime functions to achieve this. Here's a step-by-step guide: Objective-C Method Declaration First, ensure your Objective-C method is declared properly. For example: @interface Renderer : NSObject (void)mtlEnd; @end C Function to Call Objective-C Method You can define a C function that uses the Objective-C runtime to call the mtlEnd method: #include void mtlEnd(MTRenderContext mt_ctx) { // Retrieve the class of the render context Class rendererClass = mt_ctx->mt_render_funcs.mtlObj.isa; // Get the selecto

Hello ArsD, Two functions (updateMinZoomScaleForSize called from viewWillLayoutSubviews() and updateConstraintsForSize called from scrollViewDidZoom()) use the full view's bounds when they should be using the scroll view's bounds. If you use scrollView.bounds.size instead in those instances, it would account for the height occupied by the navigation bar. Thank you for your patience, Richard Yeh  Developer Technical Support

Hello RanLearns, Please create a bug report on Feedback Assistant to send us sysdiagnose logs. Once you open the bug report, please post the FB number here for my reference. The sysdiagnose should be generated shortly after the build of your app has terminated, even if the logs can't be synced off the device until later. Important: Note the date and time the issue occurred and include this information with your sysdiagnose. This information is vital in helping us pinpoint the issue being captured in the sysdiagnose log file. For information on generating and retrieving a sysdiagnose click the link below and choose the appropriate platform from the search results: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=sysdiagnose A sysdiagnose may be too large to send in e-mail. If you don't have the ability to send large files, let us know so that we can send you instructions for our Box account. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why

The documentation claims it only caches for 1 run loop turn, but as previously mentioned, that is not always the case, and certain values tend to get 'stuck.' FYI, I think there are actually two different issues at work here: The run loop itself doesn't actually turn at a predictable rate. Depending on how your app is architected and the overall app state, it's entirely possible for an app to go seconds or even minutes without the main thread ever running. The documentation says that values are automatically removed after each pass through the run loop, but that's not quite accurate. NSURL is tracking the main loop activity through a runloop observer, but it doesn't actually flush the cache until the first time something tries to access that URL from the main thread. If nothing on the main thread accesses that URL, then it could theoretically return the old values forever. ...with #2 obviously being the most significant issue. Building a cache on top of NSURL resource values, which may or may not be stale, ca

We appreciate your interest in participating in the forums! Your question seems related to Developer Account I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they check on your double charging. Albert Pascual
  Worldwide Developer Relations.