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

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.

@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

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.

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.

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.

Hi @Engineer For our bug ID- FB13970116 , Case ID- 7994770 , we have already provided additional information as asked, however we havenot got any response on possible fix either needed on app side / iOS OS side. We request to have a Code debugging session via video/screen share call with any Apple Engineer in case possible. Probably a month left in official iOS 18 release and all betas are having this persistent issue. Can you please advise on Code-level support for which request is already raised? or provide a final possible fix for this?

@Engineer

We have already shared additional information as requested on August 1, 2024.

We are still awaiting a response / feedback from your end along with any possible fix at App side or iOS OS side which is not conveyed yet. 

If there is no resolution yet, Please schedule a code-level support via Screen Share / Video call with Apple Engineer with us. 

Urgency: One of our features related to beaconing will completely stop working for all users on iOS 18 once it is released. iOS 18 release as we are expecting is in September, so we have urgency to find a resolution on this issue ASAP.

Kindly consider it on urgent basis and provide a resolution or a code-level support session.

Looking for swift response from your end.

This issue needs to be investigated by the relevant engineering teams to determine if this is a bug with iOS 18 betas.

Your Feedback is still under investigation. Until we have a resolution there will be no need for code level support, as your code seems to work fine in iOS 17 per your claims.

Also, the forums is not an appropriate place to discuss or ask about your Feedback report. Your feedback report is still under investigation. Please continue to track the problem via the Feedback Assistant.

The current status of your Feedback can be viewed in Feedback Assistant under Resolution. Here you can track if the report is still being investigated, has a potential identified fix, or has been resolved in another way.

For more details on Feedback Status, please see “Understanding Feedback Status” at https://developer.apple.com/bug-reporting/status.

@Engineer Noted! May I know is there any change or Apple Guideline for peripheral devices which are not iOS to act as beaconing device in order to intercept them by iOS 18 devices? Has any guideline or settings changed from iOS 17.5 to iOS 18 about peripheral beaconing device requirements?

Is it resolved?

I have the same problem.

Same here. Even in iOS18 Release. Any solution for that issue?

I get same issue in IOS 18, is there any solution now?