iOS 18 Simulator Crash on Xcode 26: Symbol not found: _NSUserActivityTypeBrowsingWeb

NSUserActivityTypeBrowsingWeb is not a new API, so opening a bug report would be appreciated here. Please post the FB number here for the record.

— Ed Ford,  DTS Engineer

Xcode 26.0 Beta (17A5241e) This issue continues to occur.

I've submitted a bug report as suggested — the Feedback ID is FB18393087.

Removing CoreServices.framework from Frameworks and Libraries in the Build Phases resolved the issue.

I'm having what seems to be the same or similar issue, but CoreServices.framework doesn't appear in Build Phases, any idea?

iOS 26 working great, but when I compile on iOS 18.5, I get this crash upon startup:

  Referenced from: <6D911850-31F9-34F9-A0B0-8C1A3A80FE67> /private/var/containers/Bundle/Application/3DD5AE67-E8FE-4032-B58F-BAC51485C2BA/{project}.app/{project}.debug.dylib
  Expected in:     <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices
dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib
Symbol not found: _NSUserActivityTypeBrowsingWeb
  Referenced from: <6D911850-31F9-34F9-A0B0-8C1A3A80FE67> /private/var/containers/Bundle/Application/3DD5AE67-E8FE-4032-B58F-BAC51485C2BA/{project}.app/{project}.debug.dylib
  Expected in:     <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices
dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib

@Alexander.Pan, thank you for taking the time to file the report, we really appreciate it.

— Ed Ford,  DTS Engineer

After further investigation, the origin of my crash is from FirebaseMessaging.

I'm also seeing this issue. Can also confirm removing CoreServices.framework resolves the crash, but unsure what the other implications of removing this are...?

I'm seeing the same issue on actual iOS 18 devices. Original reports seem to all explicitly mention "Simulators." Is there any value in reporting this problem as explicitly happening on-device as well? Or are we covered?

FWIW the "remove explicit CoreServices.framework" suggestion seems to do the trick...

I'm also seeing the issue. Duped because removing framework doesn't work. I think I need it for my extension to read NSURLs?? FB18733480

(My designer actually found - I usually only do beta stuff on beta, and was working in old Xcode for 18. Designer wondered how I didn't notice this bug. Which I did, as soon as I tried to run on 26 with 18 sim.)

The issue persists in Beta 4 should we just remove CoreServices.framework ? what are the implications of the removal?

@KT_, you said:

I'm also seeing the issue. Duped because removing framework doesn't work. I think I need it for my extension to read NSURLs?? FB18733480

The diagnostics you provided in that report start with this at the top:

Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView

That is an unrelated issue. Here's another forums thread regarding that.

@yonator, you said:

The issue persists in Beta 4 should we just remove CoreServices.framework ? what are the implications of the removal?

Do you have a small test project referencing NSUserActivityTypeBrowsingWeb that shows reproduces this when building your app with Xcode 26 beta 4? If so, I'd like you to attach that reproducible example to a bug report, and then post the FB number here so I can identify your specific report.

— Ed Ford,  DTS Engineer

@DTS Engineer FeedbackID: FB18299246

Thank you for opening FB18299246. I'm following up on that internally — I can also reproduce the crash using your project when using Xcode 26 beta 4 and the iOS 18.4 simulator.

— Ed Ford,  DTS Engineer

I also opened feedback FB19070326 for this issue.

As others mentioned, removing CoreServices.framework also worked for me. Just not sure if that is a permanent solution or not.

Thanks for that @donnywdavis. I'm chatting further with folks internally about this.

— Ed Ford,  DTS Engineer

I tried removing CoreServices.framework and it didn't work for me, it still crashes. What should I do?

I tried removing CoreServices.framework and it didn't work for me, it still crashes. What should I do?

Hang tight — this is a bug in the iOS SDK. Aside from removing the NSUserActivityTypeBrowsingWeb constant from your source code just as a temporary measure for your own development purposes until this is fixed, you do not need to change your project configuration.

— Ed Ford,  DTS Engineer

Could have sworn I added that I put the real FB in here a few days ago. Here's the right one, still happening on the latest betas. FB19209098

I deleted CoreServices, and now an app with iPad target runs the 18.5 simulator with latest Xcode 26 beta. However, my app with iPhone target now runs into this issue, runs fine in 18.5 release Xcode. FB19270537

After Xcode26 beta5 update now facing same crash on iOS 26 devices.

This can also be fixed by re-linking the Foundation framework. You wouldn't have to remove CoreServices in this case.

also experiencing this bug on:

• Tahoe 26.0 Beta (25A5338b)
• Xcode Version 26.0 beta 4 (17A5285i)
• iOS 26.0 (23A5318f)

dyld[945]: Symbol not found: _NSUserActivityTypeBrowsingWeb
  Referenced from: <62CC5875-13C4-3C53-80F7-A2B8FBE5D2DE> /private/var/containers/Bundle/Application/5EB5E88D-685B-4633-8716-37CD0C989111/Orders.app/Orders.debug.dylib
  Expected in:     <0FFF723A-7DE6-3705-B327-ADD82FAEF345> /System/Library/Frameworks/CoreServices.framework/CoreServices

Xcode version: 26.0 Beta 6 solved the crash for me

This seems to be fixed with Xcode 26 beta 6. I am now able to run the iOS 17 and 18 simulators, as well as build to my device again.

This seems to be fixed with Xcode 26 beta 6. I am now able to run the iOS 17 and 18 simulators, as well as build to my device again.

Excellent news! The bug reports filed by folks here were helpful in addressing this, so thank you to everyone here who took the time to file one.

— Ed Ford,  DTS Engineer