Yotta messages should track brand directly.

[jonathanolson]

Give SHA to build-an-atom (@samreid and @jbphet) to cherry-pick.

Presumably this will increment the pingver.

[jonathanolson]

Added and tested briefly above. Can you cherry-pick into a relevant phetcommon branch for build-an-atom's RC, build, and ensure that the request to immediate.gif has 'brand=phet-io'?

[jonathanolson]

SHA is 49b5cb0, so:

git cherry-pick 49b5cb0d6befc50e516598e52f4c90cb1f8be963

[jonathanolson]

Will handle on server-side in my working copy changes. My comment // Only one protocol version is currently supported will never see the light of day!

[jonathanolson]

Code to back-fill the brand server-side:

if ( protocolVersion === 2 ) {
  yottaInfo.brand = ( yottaInfo.version.indexOf( '-phetio' ) >= 0 ) ? 'phet-io' : 'phet';
}

[jbphet]

This SHA was incorporated into the Build an Atom 1.4 branch, and should now be live on the published version v1.4.0, see phetsims/build-an-atom@6c084a7. @jonathanolson - can you verify that this is working as expected?

[samreid]

It sounds like @jbphet and @jonathanolson are on the case, I'll unassign myself.

[jonathanolson]

@jonathanolson - can you verify that this is working as expected?

Build an Atom production is 1.2 (although there is a 1.4-phetio branch), and for some reason this doesn't seem to be live on the latest version of Build an Atom. Investigating.

[jonathanolson]

EDIT: Ignore this, I found the link for the wrong sim.

I'm also very confused. https://phet-io.colorado.edu/sims/beers-law-lab/1.4.0-phetio/beers-law-lab_en-phetio.html (the only 1.4 version I could find on the phet-io website) doesn't event send Yotta messages, much less include the brand with them.

[jonathanolson]

Found the right link in phet-io, confirmed that it is sending the brand.