Search results for

file uri scheme

78,602 results found

Post

Replies

Boosts

Views

Activity

Reply to lldbinit file in Xcode
Thank you! I should have noticed that. For the benefit of anyone else reading this, I have just experimented as follows. Create a file called lldbinit containing the single line settings set target.process.thread.step-avoid-regexp ^std::|^string:: Place it in the same directory as my .xcodeproj file In the field you mentioned in Product > Scheme > Info, I set the LLDB Init File field to $(SRCROOT)/lldbinit And indeed, when single-stepping, it now steps over functions in the string namespace instead of stepping into them.
Jun ’25
Reply to Child View Controllers don't get correct topLayoutGuide length
I'm sorry, I didn't explain. Just go to openradar . appspot . com and login with a Google account. I didn't put a link to avoid moderation. To simplify filing and duplicating bugs, use the excellent QuickRadar . com app. It not only allows you to file a bug simultaneously to Apple and OpenRadar but also supports the rdar URL scheme. If the respective bug is published on OpenRadar, it automatically fetches the information so you can file a dupe in just 2 seconds.
Topic: App & System Services SubTopic: General Tags:
Aug ’16
Reply to Preprocessor is Nuts
Here are some possibilities:— Wrong target membership for files that are in the project.— Incomplete or inconsistent designation of frameworks header files as private or public vs. project.— Improperly updated include or frameworks header paths in the build settings.— Improper file referencing styles for the frameworks (e.g. absolute where you need build-products-relative, etc)— Inconsistent or unexpected use of modules (off/on) for frameworks.— Incorrect or conflicting module names for frameworks (it got parameterized a couple of Xcodes ago).— Errors/inconsistencies in schemes.I'd suggest you try working through your targets individually, starting with the ones that have no other project framework dependencies, then moving on to the ones that depend on them. Check (or create) the scheme for each target, set it as the current scheme and make sure you can build each framework in turn.Worst case, you can start looking at the compiler invocation lines for steps in the
Jan ’17
Reply to UpdateApplicationContext Not Receiving updates
I don't know what was the problem but I figured out how to solve it. Basically, you need to recreate the target. In my case, I was using the old approach with watchOS app and extension app. Now Xcode 14 offers only a single target - maybe that was the problem. Steps that I used: Copy all files from your watchOS app to another location. Delete folder, target, and schemes, remove all remainings from watchOS app. Add watchOS app target using new Xcode. Add copied files from step. 1 Configure build settings, signing, and assets (whatever you need). Very important: set bundle identifier prefixed by your iOS bundle identifier. Very important: set WKCompanionAppBundleIdentifier in info.plist that equals your iOS app bundle identifier. Super important: go to your main iOS app target, general tab, frameworks, libraries... and click + and add your watchOS app. Now I like to use first watchOS scheme to install watchOS app first, then change scheme and install iOS app. Now you
Topic: App & System Services SubTopic: General Tags:
Sep ’22
Reply to Adding Widget Extension causes an error
Interesting... When creating a new project from scratch and then trying to add the extension, I've seen a dialog with the following message that hasn't shown when I was trying to add the extension in my other project: Activate “WidgetTestWidgetExtension” scheme? This scheme has been created for the “WidgetTestWidgetExtension” target. Choose Activate to use this scheme for building and debugging. Schemes can be chosen in the toolbar or Product menu. I was just trying to run the App's target because I didn't even had a scheme to run the extension's one... But if I manually create a scheme to run the extension's target, I get the same result. Yeah, I'd totally like to bump the deployment target, we might do soon, but for now, it is a requirement from the company so not much I can do there sadly... Thanks for having taken some time to look into this! 👍
Topic: App & System Services SubTopic: General Tags:
Jun ’20
Reply to Can't Find My Created File
I figured it out guys. Never mind. For debugging, you should edit the current scheme and set the working directory to something easy to find, like a folder in your home directory. (Product / Scheme / Edit Scheme / Run / Options / Use Custom Working Directory)
Nov ’21
xCode Server sometimes picks up wrong target when building test scheme
Hello everyone,We want to use xCode Server to run automated tests, and we encouter a problem here. xCode Server picks up wrong target when it builds the test scheme.Here is the details. We have three targets, call it OurApp, OurApp-ent, and AutomatedTests. The AutomatedTests target is a test target with host application being set to OurApp. A scheme called AutomatedTests is created based on the AutomatedTests target. So this scheme SHOULD only depend on the OurApp target and it should NOT depend on OurApp-ent target. If we build or run this AutomatedTests scheme within xCode, it works fine. It builds only the AutomatedTests target and the OurApp target.Then we create a Bot based on this AutomatedTests scheme. Then we have trouble. Sometimes xCode Server just builds the OurApp and AutomatedTests targets. This is correct. But SOMETIMES, xCode Server decides to build the OurApp-ent target as well, without any change in the source code or the settings! And this will fail becaus
2
0
436
Jun ’15
Context menus, alerts, popovers and tips do not respect preferred color scheme
It seems like some UI elements just don't use the preferred color scheme of their parent element: import SwiftUI struct ContentView: View { var body: some View { VStack { Button(Hold Me) { } .contextMenu(ContextMenu(menuItems: { Button(I should be dark) { } })) } .padding() .preferredColorScheme(.dark) } } If you set the device appearance to dark, then the context menu shows the correct color scheme. Setting .preferredColorScheme(.dark) to Button directly doesn't help. Aside from context menus, this applies to all sorts of elements: popovers, alerts, tips, ... Is there a workaround for this? Apple folks: FB13391355
0
0
644
Nov ’23