codesanitize

I’m making an attempt to check a characteristic that requires me to simulate my location which isn’t potential on an actual system so far as I do know. For this reason I now must construct my app, that has been working for a lot of weeks and a whole bunch of builds on my actual system, on a simulator. Nonetheless, as quickly as I begin the app within the simulator (or it will get began by Xcode), the app crashes with this log:

*** Terminating app resulting from uncaught exception 'NSInvalidArgumentException', cause: 'Couldn't discover a storyboard named 'Fundamental' in bundle NSBundle  (loaded)'
*** First throw name stack:
(
    0   CoreFoundation                      0x000000010a3677d4 __exceptionPreprocess + 172
    1   libobjc.A.dylib                     0x000000010681b7cc objc_exception_throw + 72
    2   UIKitCore                           0x0000000145d7f1f0 -[UIStoryboard name] + 0
    3   UIKitCore                           0x0000000145bd6810 -[UIApplication _storyboardInitialMenu] + 112
    4   UIKitCore                           0x0000000145bf3544 -[UIApplication buildMenuWithBuilder:] + 44
    5   UIKitCore                           0x00000001460f2cec -[UIMenuSystem _buildMenuWithBuilder:fromResponderChain:atLocation:inCoordinateSpace:] + 92
    6   UIKitCore                           0x000000014501b900 -[_UIMainMenuSystem _buildMenuWithBuilder:fromResponderChain:atLocation:inCoordinateSpace:] + 112
    7   UIKitCore                           0x00000001460f2c2c -[UIMenuSystem _newBuilderFromResponderChain:atLocation:inCoordinateSpace:] + 96
    8   UIKitCore                           0x000000014501b7d4 -[_UIMainMenuSystem _automaticallyRebuildIfNeeded] + 172
    9   UIKitCore                           0x000000014501b80c -[_UIMainMenuSystem _keyCommands] + 20
    10  UIKitCore                           0x0000000145beeeec -[UIApplication _keyCommands] + 80
    11  UIKitCore                           0x0000000145bffab0 -[UIResponder _enumerateKeyCommandsInChainWithOptions:usingBlock:] + 436
    12  UIKitCore                           0x0000000145beeb74 -[UIApplication _immediatelyUpdateSerializableKeyCommandsForResponder:] + 164
    13  UIKitCore                           0x00000001460eb9a8 -[_UIAfterCACommitBlock run] + 64
    14  UIKitCore                           0x00000001460ebdbc -[_UIAfterCACommitQueue flush] + 164
    15  UIKitCore                           0x0000000145bdf54c _runAfterCACommitDeferredBlocks + 256
    16  UIKitCore                           0x0000000145bd1028 _cleanUpAfterCAFlushAndRunDeferredBlocks + 76
    17  CoreFoundation                      0x000000010a2c7134 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 20
    18  CoreFoundation                      0x000000010a2c6898 __CFRunLoopDoBlocks + 348
    19  CoreFoundation                      0x000000010a2c1450 __CFRunLoopRun + 808
    20  CoreFoundation                      0x000000010a2c0cec CFRunLoopRunSpecific + 536
    21  GraphicsServices                    0x000000011f51ad00 GSEventRunModal + 164
    22  UIKitCore                           0x0000000145bd27d4 -[UIApplication _run] + 796
    23  UIKitCore                           0x0000000145bd6ba0 UIApplicationMain + 124
    24  UIKitCore                           0x0000000144f9cf1c block_destroy_helper.14 + 9560
    25  [...].debug.dylib                    0x0000000107067cdc $sSo21UIApplicationDelegateP5UIKitE4mainyyFZ + 128
    26  [...].debug.dylib                    0x0000000107067c4c $s4[...]11AppDelegateC5$mainyyFZ + 44
    27  [...].debug.dylib                    0x0000000107067d58 __debug_main_executable_dylib_entry_point + 28
    28  dyld                                0x00000001046113d4 start_sim + 20
    29  ???                                 0x000000010470ab98 0x0 + 4369460120
)
libc++abi: terminating resulting from uncaught exception of sort NSException
*** Terminating app resulting from uncaught exception 'NSInvalidArgumentException', cause: 'Couldn't discover a storyboard named 'Fundamental' in bundle NSBundle  (loaded)'
terminating resulting from uncaught exception of sort NSException
CoreSimulator 1010.15 - Machine: iPhone 16 Professional (7F88C881-9905-4665-AC11-282A5171CCAC) - Runtime: iOS 18.5 (22F77) - DeviceType: iPhone 16 Professional

It appears to crash as a result of my app is in search of a storyboard file, which I’ve faraway from day one, as a result of I’m doing the whole lot programatically.

Steps I’ve achieved:

1. Take away the reference to storyboard in Launch Display screen. -> Was already empty
2. Examine for any reference to “Fundamental” or Storyboard in my Data.plist -> Nothing
3. Checked if the deployment goal was set to common or something apart from iPhone -> Was already the case.

I do not know what else I can examine. AI is telling me that it may be a dependency that’s making an attempt to reference Storyboard. If that’s the case, how do I discover out which one it’s?

I am creating a .NET MAUI software concentrating on .NET 8. In my venture, I’m utilizing the next Firebase packages:

This setup works superb on each Android and iOS. Nevertheless, after I submitted my app to the App Retailer, the construct was rejected with the next message:

ITMS-91061: Lacking privateness manifest – Your app consists of “Frameworks/FirebaseABTesting.framework/FirebaseABTesting”, which incorporates FirebaseABTesting, an SDK that was recognized within the documentation as a generally used third-party SDK. If a brand new app features a generally used third-party SDK, or an app replace provides a brand new generally used third-party SDK, the SDK should embrace a privateness manifest file. Please contact the supplier of the SDK that features this file to get an up to date SDK model with a privateness manifest. For extra particulars about this coverage, together with a listing of SDKs which can be required to incorporate signatures and manifests, 
go to: https://developer.apple.com/assist/third-party-SDK-requirements.

So, primarily based on analysis and proposals, I up to date the Firebase packages to the most recent variations that presumably embrace privateness manifests:

After this replace:

• The Android construct works completely.
• However the iOS construct fails to run, with the next errors:

error : clang++ exited with code 1
error : Undefined symbols for structure arm64:
error : “_swift_FORCE_LOAD$_swiftCompatibility56″, referenced from:
error : _swift_FORCE_LOAD$swiftCompatibility56$_FirebaseAnalytics in FirebaseAnalytics
error : “_swift_FORCE_LOAD$_swiftCompatibilityConcurrency”, referenced from:
error : _swift_FORCE_LOAD$swiftCompatibilityConcurrency$_FirebaseAnalytics in FirebaseAnalytics
error : ld: image(s) not discovered for structure arm64
error : clang++: error: linker command failed with exit code 1

What I’ve Tried:

• Cleaned and rebuilt the venture.

• Verified that Xcode is updated (v16.4).

• Utilizing .NET 8 SDK (v8.0.409).

• Ensured deployment targets and iOS SDK match anticipated structure
  (arm64).

• Tried constructing each in simulator and bodily system.

How can I resolve this iOS construct failure associated to lacking Swift symbols after updating Firebase packages in a .NET MAUI venture to deal with the App Retailer’s privateness manifest requirement (ITMS-91061)?
Is there a recognized compatibility problem with Plugin.Firebase v3.x and iOS in .NET 8?

Вот переформулированный вопрос без упоминания лекарств:

Title: Flutter native notifications not firing after midnight on each iOS and Android till app is opened

Physique:

I am experiencing a problem the place scheduled native notifications cease working after midnight on each iOS and Android, however provided that the app hasn’t been opened because the notifications have been scheduled.

State of affairs:

1. Consumer interacts with the app in the course of the day and completes a number of duties
2. Every accomplished job schedules a notification for a similar time subsequent day
3. Consumer closes the app within the night (e.g., 21:00) and would not open it once more
4. Subsequent morning, NO notifications arrive at scheduled occasions
5. BUT if consumer opens the app even briefly after midnight, all subsequent notifications for that day work completely

Present implementation:

• Utilizing flutter_local_notifications package deal
• Scheduling with flutterLocalNotificationsPlugin.zonedSchedule()
• Utilizing AndroidScheduleMode.alarmClock for Android
• Notifications are scheduled accurately (verified with debug logs)

Testing outcomes:

• Works completely in emulator even when altering system time
• Works on bodily gadget when manually altering time
• Fails solely in real-world situation when gadget sleeps in a single day
• Similar conduct on each iOS and Android

Code snippet:

await flutterLocalNotificationsPlugin.zonedSchedule(
  notificationId,
  title,
  physique,
  tzDateTime,
  notificationDetails,
  payload: payload,
  uiLocalNotificationDateInterpretation:
      UILocalNotificationDateInterpretation.absoluteTime,
  androidScheduleMode: AndroidScheduleMode.alarmClock,
);

It looks as if the OS is killing scheduled notifications in the course of the evening. Has anybody skilled this? What is the correct manner to make sure notifications survive in a single day with out opening the app?