Are several Proximity and Beacon related libraries methods and properties deprectaed and now unusable in iOS 18 beta?

Question

gaurav_mishra2 OP

Created Jun ’24

Replies 5

Boosts 0

Participants 2

Hi,

Please let me know iOS 18 beta have deprecated/ stopped support for which of the following:

proximityUUID
CLBeaconRegion
- (instancetype)initWithProximityUUID:(NSUUID *)proximityUUID identifier:(NSString *)identifier
- (void)startRangingBeaconsInRegion:(CLBeaconRegion *)region
-startRangingBeaconsSatisfyingConstraint: , is this also deprecated in iOS 18 beta, since: CLBeaconIdentityConstraint is deprecated right?
CLBeaconIdentityCondition is not supported in XCode 15.3. What should I do for this? Should I install XCode 16 beta?
locationManager:didRangeBeacons:satisfyingConstraint: can we use it in iOS 18 beta, since, CLBeaconIdentityConstraint is deprecated? what is alternative
startMonitoring(for:) is also deprecated in iOS 18 beta right?

Also, can someone specify or create a documentation on how beaconing shall be monitored, ranged and locationManager delegate methods pertaining to beaconing to be used in iOS 18 beta?

Boost

Answer 1

Engineer OP

Apple

Jun ’24

CLBeaconRegion and its family of calls and definitions are soft deprecated, meaning they are still supported in iOS 17 and 18 although there is a new and improved replacement API for it.

You can still use the old API until comes an iOS version that no longer supports it. The new APIs cannot be used in versions earlier than when they have been announced at.

0

Answer 2

gaurav_mishra2 OP

Jun ’24

@DTS Engineer The delegate method :

locationManager(_ manager: CLLocationManager, didRangeBeacons beacons: [CLBeacon], in region: CLBeaconRegion)

is giving no values in beacons for iOS 18 beta iPhone device in XCode 16 beta while the same code works and gives correct beacons on same peripheral and central devices in iOS 17. Has something changed in iOS 18 beta or is it iOS 18 beta bug related to beacons? @DTS Engineer

0

Answer 3

Engineer OP

Apple

3w

Our engineering teams need to investigate this issue, as this might indicate an issue with iOS 18 Beta.

We'd greatly appreciate it if you could open a bug report, include as much detail to help reproduce the issue, and post the FB number here once you do.

Bug Reporting: How and Why? has tips on creating a successful bug report.

0

Answer 4

gaurav_mishra2 OP

3w

Hi @DTS Engineer Thanks for acknowledging to investigate the iOS 18 beta issue. We have already created a bug on Feedback Assistant App, with** FeedBack ID :**** FB13970116**, having all the details. We have also requested for a code-level support with** Case-ID:**** 7994770**. We request to have a virtual call with an Apple Engineer for a quicker resolution, as this is a high impact issue for Business and Customer Satisfaction for the Organisation. We shall be happy to share screen and walkthrough all functions and impacted code, in case needed.

0

Answer 5

gaurav_mishra2 OP

1w

Hi @Engineer , We haven't got a response on above request to have code-level support, also there is no update on what is the outcome of investigation undertaken for this issue in iOS 18 beta 1. There is no feedback on Feedback Assistant app also regarding this. Kindly highlight if any update is there on the query. CASE ID: 7994770, FEEDBACK ID:L FB13970116.

0