Home Blog Page 4

set up NATIVE iOS mapbox navigation SDK in EXPO


Is there any means to make use of the native iOS mapbox navigation sdk in an expo module WITHOUT utilizing a 3rd celebration expo or react-native package deal?

I am following this expo information on Wrap third-party native libraries , attempting to make use of the mapbox ios navigation sdk, which appears to be solely out there through SPM, not Cocoapods (right here mapbox says “CocoaPods help is at present in improvement and can be added in future variations.”).

I’ve arrange the ~/.netrc file with my non-public mapbox key.
I’ve additionally created a config plugin that efficiently provides all vital values to the Data.plist recordsdata as instructed within the Mission Configuration half.

That is my config plugin withMapboxToken.js:

const { withInfoPlist } = require('@expo/config-plugins');

const withMapboxToken = (config) => {
  return withInfoPlist(config, (config) => {
    // Add Mapbox entry token
    config.modResults.MBXAccessToken = course of.env.MAPBOX_PUBLIC_TOKEN;
    
    // Add location permissions
    config.modResults.NSLocationWhenInUseUsageDescription = 
      "Reveals your location on the map and helps enhance the map.";
    
    config.modResults.NSLocationAlwaysAndWhenInUseUsageDescription = 
      "Reveals your location on the map and helps enhance the map.";

    // Add background modes for audio and site updates
    if (!config.modResults.UIBackgroundModes) {
      config.modResults.UIBackgroundModes = [];
    }
    
    if (!config.modResults.UIBackgroundModes.consists of('audio')) {
      config.modResults.UIBackgroundModes.push('audio');
    }
    
    if (!config.modResults.UIBackgroundModes.consists of('location')) {
      config.modResults.UIBackgroundModes.push('location');
    }

    console.log('✅ Mapbox token and permissions configured');
    return config;
  });
};

module.exports = withMapboxToken; 

There appears to be no downside regarding the linking/bridging between native iOS and XCode, as I efficiently managed to jot down a Easy “Hey World” view in Swift, which reveals up within the expo improvement construct.
Now, when attempting to put in the SDK, this appears to be the half the place I fail.
I first tried all methods I may assume (handbook set up in XCode, or utilizing a Bundle.swift file) of to first MANUALLY set up the SDK and have a improvement construct working on my iPhone with none issues.

Remember the fact that I am utilizing expo managed workflow, so the ios/ and android/ folders are mechanically generated and should not be manually modified, I even have them in my .gitignore. I simply needed to strive manually putting in the SDK first, earlier than attempting to automate this for instance through a config plugin or a script that I run after prebuild and earlier than creating a brand new improvement construct.

When attempting to run npx expo run:ios --device , I get this error within the output:

  1 | import ExpoModulesCore
> 2 | import MapboxDirections
    |        ^ no such module 'MapboxDirections'
  3 | import MapboxNavigationCore
  4 | import MapboxNavigationUIKit
  5 | import UIKit

› Compiling expo-linking Pods/ExpoLinking » ExpoLinking-dummy.m

› 1 error(s), and 1 warning(s)

CommandError: Didn't construct iOS undertaking. "xcodebuild" exited with error code 65.

So it appears to me the Swift package deal(s) haven’t been accurately put in.
And that is what the “Bundle Dependencies” a part of my XCode Mission Navigator appears to be like like:
8

SFL to Ship Fast Deployment AISSat-4 for Norway’s Increasing Maritime Surveillance


SFL to Ship Fast Deployment AISSat-4 for Norway’s Increasing Maritime Surveillance

by Clarence Oxford

Los Angeles CA (SPX) Jul 30, 2025






SFL Missions Inc. has secured a contract from the Norwegian House Company (NOSA) to develop AISSat-4, a ship-tracking nanosatellite scheduled for launch inside a 12 months. The mission goals to bolster Norway’s maritime monitoring community by including capability as present satellites strategy the tip of their service lives.



Constructed on SFL’s confirmed SPARTAN 6U platform, AISSat-4 will carry a single Computerized Identification System (AIS) receiver developed by Kongsberg Seatex of Trondheim. The SPARTAN bus has a robust monitor file, with 18 industrial satellites launched so far.



SFL’s vertically built-in construction permits fast growth, testing, and deployment. “We’ve in depth expertise in implementing AIS missions, and due to this fact we have now the experience and design heritage wanted to implement the AISSat-4 mission on a brief schedule,” mentioned Dr. Robert E. Zee, SFL Missions Director and CEO.



The AISSat-4 satellite tv for pc will seize as much as 1.5 million distinctive AIS indicators each day, even in busy maritime corridors. It should reinforce Norway’s Blue Justice Ocean Surveillance Program, which permits nations to share space-based AIS knowledge to fight unlawful fishing and maritime crime globally.



Norway operates one of many world’s most superior space-based marine surveillance methods by NOSA and the Norwegian Coastal Administration. “The societal advantages we achieve from accumulating AIS data from satellites is critical. It’s due to this fact essential that we guarantee the upkeep of this functionality,” mentioned Coastal Administration Director Einar Vik Arset.



The Norwegian house AIS fleet started with AISSat-1 in 2010, which collected knowledge for 12 years. It was adopted by AISSat-2, NorSat-1 and -2 in 2017, NorSat-3 in 2021, NorSat-TD in 2023, and NorSat-4 in early 2025. These satellites built-in more and more superior applied sciences together with radar detectors, optical cameras, laser communications, and fifth-generation AIS receivers.



The upcoming AISSat-4 satellite tv for pc will focus solely on AIS knowledge assortment, persevering with the legacy of space-based maritime situational consciousness initiated over 15 years in the past in partnership with SFL.


Associated Hyperlinks

SFL Missions

Naval Warfare within the twenty first Century



xcode – Why is my iOS app construct engaged on an actual system, however crashing on a simulator?


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?

.NET MAUI iOS Construct Fails with Firebase v3.x as a consequence of Lacking Swift Symbols After Updating to Repair ITMS-91061 (Privateness Manifest)


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?

Survey: AI, cyber threats, distributed workforces problem IT groups most



Key elements behind insufficient difficulty prevention and mitigation embrace:

  • Inefficient workflows sluggish difficulty response: 53%
  • Understaffing as a key problem: 36%
  • Lack the appropriate instruments: 13%

“Corporations usually default to fixing issues with know-how first. But when they don’t get the outcomes they have been anticipating, they’re left questioning why. So whereas they might purchase the best-in-class device to resolve all their issues, they have a tendency to neglect about how folks leverage the instruments. They purchase seats however neglect the folks sitting in them.” Gazarek said within the report.

Important points result in poor buyer expertise

Penalties of poor operational resilience usually fall on prospects, in response to the report.

The survey discovered that 71% of respondents word buyer expertise as a core concern stemming from vital points and programs outages. About one-third (32%) of these surveyed stated they misplaced income from outages and different vital points, and greater than one-quarter (28%) cited model harm on account of poor efficiency and buyer expertise.

Greater than half (55%) of organizations measure efficiency metrics equivalent to imply time to detect, acknowledge, or restore (MTTx), however 45% of these surveyed reported they don’t monitor MTTx metrics. Among the many most typical the explanation why respondents don’t use MTTx embrace:

  • Lack of expertise: 38%
  • Difficultly measuring precisely: 16%
  • Favor different efficiency metrics: 16%
  • Not related to operational targets: 14%
  • Useful resource constraints stopping implementation: 8%
  • Would spotlight deficiencies: 6%

Of these respondents measuring efficiency metrics, practically one-quarter (73%) say that instruments have the best influence on decreasing MTTx, workflows are available an in depth second (67%), and groups land in third place, with 44% saying folks play the most important function in decreasing MTTx metrics.