title: Send FCM from one Firebase account to apps compiled w/ different package names
body: <p>This may really be more of a branding question but I'm asking here because it has to do with how FCM handles notifications.</p>
  <p>We have an app that sends notifications to users based on the topic they subscribe to. The topics are specific to our customers who are businesses themselves. So the relationship is:</p>
  <pre><code>Our Company -&gt; Other Company (our customers) -&gt; Other Company's Customers (end users)
  </code></pre>
  <p>Say we have &quot;Other Company A&quot; and &quot;Other Company B&quot; with topics &quot;A&quot; and &quot;B&quot;. Company A can use our system to send notifications to it's customers, and Company B can do the same. When their customer (end user) downloads and opens the app, they put in a topic A or B. This subscribes to the topic and also downloads that particular company's image, info, etc. so it is semi-branded for that company.</p>
  <p>Now those companies want the app to show up in their own app/play stores. So we re-compiled the app changing the package name from com..app to com..app to submit to their stores even though that seemed like a brute force approach. But now notifications do not go through to the newly compiled apps.</p>
  <p>I'm not sure what needs to change so that notifications can be sent from the same Firebase service to differently compiled apps?</p>
  <p>And I guess the higher-level question would be is this even the correct approach for taking the app and branding it for a customer? The business only wants their customers (the end users) to see the app in their store instead of ours, and to have their image saved on the mobile devices instead of our company image when the app is installed.</p>
  <p>Any guidance would be greatly appreciated!</p>