Still broken in iOS 18.2 simulator…
Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for
167,447 results found
Post
Replies
Boosts
Views
Activity
I found a solution that works fine for me: In terminal type: defaults write com.apple.LaunchServices LSHandlers -array-add LSHandlerContentTag gpxLSHandlerContentTagClass public.filename-extensionLSHandlerRoleAll com.apple.dt.document.gpx then /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -domain local -domain system -domain user
I don't think it's hard to do this in AppKit. It's just different. I haven't done this in awhile. But I'm pretty sure you could use NSSplitViewController. @interface NSSplitViewController (NSSplitViewControllerToggleSidebarAction) /// Animatedly collapses or uncollapses the first sidebar split view item in the receiver. Does nothing if the receiver does not contain any sidebars. - (IBAction)toggleSidebar:(nullable id)sender API_AVAILABLE(macos(10.11)); /// Animatedly collapses or uncollapses the first inspector split view item in the receiver. Does nothing if the receiver does not contain any inspectors. - (IBAction)toggleInspector:(nullable id)sender API_AVAILABLE(macos(14.0)); @end To get the toggle sidebar button in the toolbar you need to build an NSToolbar on your window. You could do this in Interface Builder or programmatically. Add a toolbar item to the toolbar with the following identifier: // A standard item that is configured to send -toggleSidebar: to the firstResponder when invoked. APPK
Should I mail the link to the test project.
Hello, I am having the following issue: I am using the packages DSWaveformImage and DSWaveformImageViews if that matters. My code's goal is to generate waveform images from files embedded in the application. That works great on a simulator device, but when I run the code on a physical device (iPhone 15 Pro, iOS 18.2), I get this error (shown in the attached screenshot below):
Just to be clear this fix doesn't work for ios 18.3 only ios 18.0.3
I'm having the same problem now for an advanced app clip experience I submitted a week ago. Older app clips with the same URL but a different query parameter are working fine. Does Apple really support app clips any more? They were first available with iOS 14 and the process is still buggy and frustrating. They should at least give some guidance on what Received means and how long to reasonably wait before it's working.
Hi, Sorry to hear you are having problems getting previews working. To verify that the simulators work outside of previews on your system could you attempt a build+run of your app ⌘+R ? If that works then the best next step will be to file a feedback with diagnostics so we can take a look. We will need the diagnostics Xcode Previews generates in order to make sure we understand the error the previews system is encountering. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics butto
I am working with an open source watch called PineTime to implement ANCS support so users can receive iOS notifications in the watch. I am having g trouble discovering the ANCS on an iOS device. The watch is properly paired and bonded. I realize that the ANCS may not always be present, so I also subscribed to the GATT Service changed characteristic, but never received a notification/indication for a service becoming active. Is there something I am missing? Thanks!
I can also confirm that the same thing is happening when communicating from the app to the watch: the watch app wakes in background to process data from the iPhone app and calls reloadAllTimelines, but the watch face complication does not reload. I'm guessing this is an iOS 18 bug because I've only heard from my customers in the last few weeks about this.
Hi everyone, I am a beginner in iOS/Swift programming. I'm trying to develop a mobile application that allows to mount a network drive in the iphone Files application via the WebDav protocol. I saw on the internet that WebDav is no longer implemented in iOS because considered deprecated by apple. To accomplish this task, I decided to separate responsibilities as follows: Framework: WebDav (responsible for communication with the WebDav server) FileProviderExtension: FileBridge (Responsible for bridging the gap between the WebDav Framework and the iOS Files app) Main App I also have an AppGroup that includes the main application and the fileproviderextension Initially, to measure the feasibility and complexity of this task, I'd like to make a simplistic version that simply displays the files on my drive in the Files app, without necessarily being able to interact with them. FileProviderExtension.swift: import FileProvider import WebDav class FileProviderExtension: NS
Hi, the new style of tab bar is at top, sort of a picker style , how to enforce SwiftUI to use it in old style fashion at bottom in iPadOS same as iOS ? — Kind Regards
I had this problem on iOS 18.2. I fixed my changing the order of my keyboards in the general space keyboard setting.
When I try to run my project on the simulator, it tells me there is a bug. It is not in the code I wrote, but I believe in the compiler. It would work perfectly, say the build succeeded, but the phone turns white and stops there. I don't know how to debunk it, what to do! Picture of what happens with the phone: Picture of the debugging area:
I use AppIntent to trigger a widget refresh, Appint is used on Button or Toggle,as follows var isAudibleArming = false struct SoundAlarmIntent: AppIntent { static var title: LocalizedStringResource = SoundAlarmIntent func perform() async throws -> some IntentResult { isAudibleArming = true return .result() } } func timeline( for configuration: DynamicIntentWidgetPersonIntent, in context: Context ) async -> Timeline { var entries: [Entry] = [] let currentDate = Date() let entry = Entry(person: person(for: configuration)) entries.append(entry) if isAudibleArming { let entry2 = Entry(person: Person(name: Friend4, dateOfBirth: currentDate.adding(.second, value: 6))) entries.append(entry2) } return .init(entries: entries, policy: .never) } The timeline function fires, with entry corresponding to view1 and entry2 corresponding to view2. I expect to show view1 immediately and view2 6 seconds later. You get the correct response on iOS17. But the 6 second delay function on the discovery code in iOS18.2 takes eff