`accept-language` is not send correctly by URLSession

Question

Created Sep ’22

Replies 4

Boosts 0

Views 2.7k

Participants 3

We are developing an multi language app. We support

When the user have set the phones primary language to Danish and the secondary language to French, the app will then default to French.

URLSession will then put da-DK,da;q=0.9 in the accept-language header and not fr-FR,fr;q=0.9 as expected.

But when the user changes the app only to German, then the accept-language header is de-DE,de;q=0.9

So it looks like iOS is not sending the correct header.

Anyone else that have experienced this problem and maybe can help us?

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’22

I’d like to clarify this:

When the user have set the phones primary language …

But when the user changes the app only to German …

My reading of this is that:

URLSession does the right thing when you change the language for the system as a whole.
But the wrong thing when you change the language just for your app.

Is that correct?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

Sep ’22

Hi Quinn!

Thanks for the reply.

My iOS language settings are the following screenshot

Simulator Screen Shot - iPhone 14 Pro - 2022-09-27 at 10.57.12.png

The app language setting are the following screenshot

Simulator Screen Shot - iPhone 14 Pro - 2022-09-27 at 10.57.22.png

Here I would expect that URLSession is adding fr-FR,fr;q=0.9 as accept-language header. But it actually sends da-DA,da;q=0.9.

When we change the language to English or German, we get the correct headers as expected

0

Answer 3

DTS Engineer OP

Apple

Sep ’22

That seems like a bug to me and I encourage you to file it as such. Please post your bug number, just for the record.

Here I would expect that URLSession is adding fr-FR,fr;q=0.9

You mean fr-CH,fr;q=0.9, right?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 4

Oct ’22

Bug filed: FB11640290

0