Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Hi, I'm new to BDS and have a quick question. I have an application that I'm hoping to distribute to multiple carriers. The application (mod/mif/bar) will be identical across carriers, but there will be some slight configuration differences. (the configuration lives in a text file in the mod directory).

My question is this: can I get away with putting my app through NSTL just once, and distribute the same signed binary with different versions of the config file to different carriers? Is the BDS set up to do something like that? Or am I stuck paying NSTL for each configuration I want to release?

I thought there was a separate price for testing apps which had only minor changes (i.e. no change to the binary). Take a look at the TBT charge sheet.

I thought there was a separate price for testing apps which had only minor changes (i.e. no change to the binary). Take a look at the TBT charge sheet.

You need to submit multiple times.
TheDude wrote:Hi, I'm new to BDS and have a quick question. I have an application that I'm hoping to distribute to multiple carriers. The application (mod/mif/bar) will be identical across carriers, but there will be some slight configuration differences. (the configuration lives in a text file in the mod directory).
My question is this: can I get away with putting my app through NSTL just once, and distribute the same signed binary with different versions of the config file to different carriers? Is the BDS set up to do something like that? Or am I stuck paying NSTL for each configuration I want to release?

You need to submit multiple times.
TheDude wrote:Hi, I'm new to BDS and have a quick question. I have an application that I'm hoping to distribute to multiple carriers. The application (mod/mif/bar) will be identical across carriers, but there will be some slight configuration differences. (the configuration lives in a text file in the mod directory).
My question is this: can I get away with putting my app through NSTL just once, and distribute the same signed binary with different versions of the config file to different carriers? Is the BDS set up to do something like that? Or am I stuck paying NSTL for each configuration I want to release?