@KayleeSC How did you get the bloomFilter hash correct? I followed your process from earlier in this thread. I used the MurmurHash3 swift library, but the standard FNV-1a implementation instead of the inverted order of operations you suggested. (An apple dev told me to do it this way) The hash this produces still isn't blocking sites for me. Is this the hash you got for the 10 example websites in the starter code? UzDsxTWvY7Y/grhkQS1KZe8SslPAGOFK

I had this error. I was using the PIRService from the example code. The fix: remove https:// in favour of http:// in the server config url in your filter app. Since you're running the PIRServer (presumably) on a local network, https won't work.

Lol, I figured it out. It was my mistake. I had a previous iteration of the app that had a different bundle ID, which was still installed, lingering on my phone. I deleted that one and it the pesky filter associated with it went away.

It does not. The app, while installed, can remove the filter for me. However if the app gets uninstalled, the filter persists and the next iteration of the app that gets installed is not able to remove it either.

@anton_kliukin It stopped happening to me after I updated to the newest beta (it was 26.1 beta 5 at the time I believe). Unfortunately there has been no update on my bug report, so if this is still happening for you, I don't know if there's anything you can do except submitting your own bug report.

Any update on this? When can we expect the next version of the sample project?

I am testing on iOS 26. I have reproduced the bug and collected a sysdiagnose (thank you for your guidance). I have uploaded the sysdiagnose to my bug report, so if you could get my ticket back in the loop I'd appreciate it. Thanks!

I see that another developer has also run into this issue: https://developer.apple.com/forums/thread/791352?answerId=847563022#847563022 The suggested fix of quitting the Settings app before configuring the app did not work for me. I've submitted a bug report: FB20479096

Was struggling for hours before discovering this thread. The issue for me was for literally any app i tried to upload, not just one specific app. I did discover a workaround. WORKAROUND: Go to Certificates, Identifiers & Profiles Create a profile that specifically targets your app bundle identifier create the profile, download it disable automatic profile management in xcode under Signing & Capabilities Import newly downloaded profile worked for me :)