Incorrect Software Version Displayed in Processing Log

RE: Incorrect Software Version Displayed in Processing Log

Natasha_C — Wed, 18 Feb 2026 22:39:40 GMT

Hi Shogo,

I’m sorry to hear that the update did not resolve the issue.

We’ll take a closer look and follow up with you, most likely next week, with an update.

Thank you for your patience!

RE: Incorrect Software Version Displayed in Processing Log

a.da — Thu, 12 Feb 2026 00:36:56 GMT

Hi Noah,

Unfortunately, even after updating the iOS app to v1.14.0, I did not get the expected result.

The behavior remains unchanged from before; the version is still displayed as "0.0.1 0" in the OTA events.

To make sure we are on the same page, could you clarify if my understanding of the fix is correct?
I expected that if 'CONFIG_BT_DIS_FW_REV_STR' is set to "0.0.1+0", it should now be displayed exactly as "0.0.1+0".
Is this the intended behavior of the new update?

I apologize for the repeated inquiries on this matter, and I truly appreciate your continued support.

a.da

RE: Incorrect Software Version Displayed in Processing Log

NoahPendleton — Tue, 10 Feb 2026 21:52:44 GMT

Hi a.da -

Just wanted to let you know, we have a new release of nRF Connect Device Manager for iOS, v1.14.0, that includes the fix for the `+` character in version strings.

apps.apple.com/.../id1519423539

Thanks!
Noah

RE: Incorrect Software Version Displayed in Processing Log

NoahPendleton — Mon, 09 Feb 2026 16:17:57 GMT

Hi a.da -

Thanks for trying it out, and figuring out the workaround! Indeed it is the BT DIS value the mobile app is using for firmware version. All versions should be synchronized, i.e. this section of the sample `prj.conf`:

# Set MCUBoot image header version to match DIS and Memfault version CONFIG_BT_DIS_FW_REV_STR="0.0.1" CONFIG_MEMFAULT_NCS_FW_VERSION_STATIC=y CONFIG_MEMFAULT_NCS_FW_VERSION="0.0.1" CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION="0.0.1"

Regarding this:

> First, even after redefining the default value in my project’s 'Kconfig' file

This usually means the `source "Kconfig.zephyr"` line preceded where you tried to override the default. If you keep that at the end, it should work:

https://github.com/memfault/memfault-firmware-sdk/blob/050c1a5748f9c668cb1c152735438596e528ad9c/examples/nrf-connect-sdk/nrf5/memfault_demo_app/Kconfig#L99

But you will need to make sure you include all settings, i.e:

config MEMFAULT_NCS_FW_VERSION default "$(VERSION_MAJOR).$(VERSION_MINOR).$(PATCHLEVEL)"
config MCUBOOT_IMGTOOL_SIGN_VERSION
default MEMFAULT_NCS_FW_VERSION
config BT_DIS_FW_REV_STR
default MEMFAULT_NCS_FW_VERSION

On the iOS app update- we've made the changes and will be releasing the app shortly. It can take a few days to be available on the app store, we'll let you know when it's ready to update!

And thank you very much for your patience, and for providing the excellent bug report, greatly appreciated!

Thanks,

Noah

RE: Incorrect Software Version Displayed in Processing Log

a.da — Fri, 06 Feb 2026 05:02:47 GMT

Hi Noah, thanks for your reply.

I tried the suggested workaround and found two important points:

First, even after redefining the default value in my project’s 'Kconfig' file, the value remained "0.0.1+0" and did not change.

config MEMFAULT_NCS_FW_VERSION
	default "$(VERSION_MAJOR).$(VERSION_MINOR).$(PATCHLEVEL)"

I suspect this is because the initial value was already determined when it was declared within the NCS ( nRF Connect SDK ) environment.

C:\ncs\v3.2.1\nrf\modules\memfault-firmware-sdk\Kconfig

config MEMFAULT_NCS_FW_VERSION
	string "Static firmware version to use"
	depends on MEMFAULT_NCS_FW_VERSION_STATIC
	default "$(APP_VERSION_TWEAK_STRING)" if "$(VERSION_MAJOR)" != ""

However, when I set a fixed value in 'prj.conf' file instead of the 'Kconfig' file, it worked as expected.

CONFIG_MEMFAULT_NCS_FW_VERSION="0.0.1"

Second, it appears that the value displayed in the "OTA check for update events" log is actually 'CONFIG_BT_DIS_FW_REV_STR', not 'CONFIG_MEMFAULT_NCS_FW_VERSION'.

As mentioned earlier, even when I set 'CONFIG_MEMFAULT_NCS_FW_VERSION' to a fixed value ( "0.0.1" ), the version in the OTA events was still displayed as "0.0.1 0".
After setting 'CONFIG_BT_DIS_FW_REV_STR' to the same fixed value, it was correctly displayed as "0.0.1".

CONFIG_MEMFAULT_NCS_FW_VERSION="0.0.1"
CONFIG_BT_DIS_FW_REV_STR="0.0.1"

I look forward to the mobile app update!

a.da

RE: Incorrect Software Version Displayed in Processing Log

NoahPendleton — Thu, 05 Feb 2026 21:45:45 GMT

Hi a.da-

Thank you for reporting this issue!

It looks like there's an incompatibility in nRF Connect Device Manager iOS application when the software version contains a non-URL-safe character, in this case `+`.

Since you're using the automatic version number from `VERSION` file, you can use a small workaround in your project's `Kconfig` file to eliminate the `+0` component of the version, see an example here:

https://github.com/memfault/memfault-firmware-sdk/blob/master/examples/nrf-connect-sdk/nrf5/memfault_demo_app/Kconfig#L55-L97

This sets the `MEMFAULT_NCS_FW_VERSION` value to match `MEMFAULT_BUILTIN_DEVICE_INFO_SOFTWARE_VERSION`. `MEMFAULT_BUILTIN_DEVICE_INFO_SOFTWARE_VERSION` is set here:

https://github.com/memfault/memfault-firmware-sdk/blob/master/ports/zephyr/Kconfig#L1053

You can see the strategy there, which doesn't populate the `+0` if it's `=0`, which will remove the extraneous `+0` from the version number passed by the mobile app.

We'll work on an update for the mobile app to properly solve the problem long-term.

Thanks!

Noah

RE: Incorrect Software Version Displayed in Processing Log

Simon D-M — Thu, 05 Feb 2026 12:39:39 GMT

Hi,

I tried to reproduce your error, but wasn't able to reproduce it, unfortunately. I'll forward this internally. I or a colleague will get back to you soon.

Best regards,

Simon D-M

RE: Incorrect Software Version Displayed in Processing Log

a.da — Thu, 05 Feb 2026 01:40:28 GMT

Hi Simon D-M, thanks for your reply.

I have attached my project.

I applied the Memfault Docs Quickstart to the MDS sample program.

Additionally, I modified some Kconfig default values to reference other Kconfig values.

I also Added a new VERSION file.

This is so to avoid hardcoding the same value multiple times.

devzone.nordicsemi.com/.../peripheral_5F00_mds.zip

a.da

RE: Incorrect Software Version Displayed in Processing Log

Simon D-M — Wed, 04 Feb 2026 14:35:21 GMT

Hi,

Can you please zip and share your project (remove your memfault project key before sending it), so that I can try to reproduce your bug?

Because, by default this sample doesn't support FOTA, I just want to see the change that you did and try it on my end.

I can make this ticket private if you are not comfortable sharing your project publicly :)

Best regards,

Simon D-M