Thanks for being a part of WWDC25!

How did we do? We’d love to know your thoughts on this year’s conference. Take the survey here

Unexpected app version in logs — does MARKETING_VERSION change dynamically?

Hello,

I've encountered unexpected behavior related to version information in our app logs, and I'd like to ask for some advice.

We reviewed logs collected from a user running our app (currently available on the App Store). The logs are designed to include both the build number and the app version.

Based on the build number in the logs, we believe the installed app version on the user's device is 1.0.3. However, the app version recorded in the logs is 1.1.5, which is the latest version currently available on the App Store.

In our project, we set the app version using the MARKETING_VERSION environment variable. This value is configured via XcodeGen, and we define it in a YAML file.

Under normal circumstances, the value defined in the YAML file (MARKETING_VERSION = 1.0.3) should be embedded in the app and reflected in the logs. But in this case, the version from the current App Store release (1.1.5) appears instead, which was unexpected.

We'd like to know what might cause this behavior, and if there are any known factors that could lead to this. Also, is it possible that MARKETING_VERSION might somehow dynamically reflect the version currently available on the App Store?

YAML:

info.plist:

Unexpected app version in logs — does MARKETING_VERSION change dynamically?
 
 
Q