6

Custom iPhone device name not respected by NextDNS app

Setting a custom iPhone name in the settings is not used by the Nextdns app in the logs and it appears as the default name.

 

   

13 replies

null
    • Michael_Roesch
    • 2 yrs ago
    • Reported - view

    Came here to report the exact same problem. I'm kinda worried that the app won't receive a timely update, because as it has been said here already, the last app update was from a year ago. Seems abandoned to me

    • Pierre_Cartier
    • 2 yrs ago
    • Reported - view

    If I look at the screenshots I am not sure you guys are following the right process. 

    NextDNS doesn't pickup your iPhone name within iOS settings.  

    Your device name must be filled in within NextDNS settings, we screenshot. 

      • Michael_Roesch
      • 2 yrs ago
      • Reported - view

      Pierre Cartier Looking at your screenshot and reply, you don't understand what this issue is about, no offense. 😉

      In the past the iOS app absolutely did pick up the correct device name, hence the setting in the iOS app "Send Device Name". It lost this ability somewhere down the road, probably with the release of iOS 16. 

      What you are referring to is a custom configuration name, "iPhone" in your case, which has nothing to do with OPs or my problem described. 

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      Michael Roesch Sorry I didn't notice you were using NextDNS app that I do not use. So if the problem is coming from the application you might want to use NextDNS  address with your device name in it as a workaround...? I am managing 5 profils /devices  like that with no issue. 

    • Michael_Roesch
    • 2 yrs ago
    • Reported - view

    @mike_brust  You should remove your device serial from the screenshot 

      • Mike_Brust
      • 2 yrs ago
      • Reported - view

      Michael Roesch Hi Michael, you mean the model number ? That's not critical

    • D_K
    • 2 yrs ago
    • Reported - view

    I am seeing the same behavior. The Device list just says "iPhone 12" instead of the device's assigned name. Considering there are multiple iPhone 12s on my network, this is less than ideal.

    • teal_rabbit
    • 2 yrs ago
    • Reported - view

    Sadly a 'known issue' I reported back when on iOS16 Beta.

    iOS 16 Beta isn't using device name - Bug Reports - NextDNS Help Center

    • valch85
    • 1 yr ago
    • Reported - view

    Dear nextdns developers, is there any eta for this bug fix ?

    • Tin.1
    • 1 yr ago
    • Reported - view

    Same issue

    • brian163
    • 10 mths ago
    • Reported - view

    Considering this issue is over a year old, does the development team EVER provide acknowledgements or ETAs on bug fixes on these forums? I' m just curious. 🤔

    • Zeki
    • 6 days ago
    • Reported - view

    The error still persists. I will start using ControlD just for this reason.

      • Failsafe
      • 6 days ago
      • Reported - view

       Not that you asked for my opinion, but it seems like somewhat of a petty reason to jump ship from a very solid service. I get that customer service isn't great right now, but it's not all rainbows and unicorns at Control D, either. To each their own.

      I would pose the question as to why the NextDNS app is more preferred over creating and using a Profile using: 

      https://apple.nextdns.io

      You can specify the device name in the profile. This is the recommended way forward from NextDNS and has the added advantage of not having the overhead of running another app on your phone.
       

      For the techies here:
      The underlying issue is that beginning with iOS 16 the exact "name" property (name of the device) became inaccessible for apps that are not built with an entitlement for:

      com.apple.developer.device-information.user-assigned-device-name

      There is a process to get your app entitled and approved for accessing the device's user-assigned name. Otherwise, the default without that entitlement is... you guessed it... 'iPhone'.

      This does require @NextDNS rolling a new update to get this fixed.

      See here for more info:

      https://developer.apple.com/documentation/uikit/uidevice/name
Login to reply

Content aside

  • 6 Votes
  • 6 days agoLast active
  • 13Replies
  • 1073Views
  • 11 Following