Answers.Body: <p>You probably just need to clear the Craft <code>storage/cache</code> folder on production.</p>
  <p>Licensing info is cached for 24 hours at a time.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-18T13:29:45.567Z
Answers.Text: This is a good rule of thumb which I completely blanked on yesterday. Thank you sir.
Answers.UserDisplayName: Vaughn D. Taylor
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-17T18:29:50.480Z
Answers.LastActivityDate: 2020-06-17T18:29:50.480Z
Answers.UserDisplayName: Brad Bell
Body: <p>In my production environment, I have administrative changes disabled, so I see the following messages:</p>
  <pre><code>* You’re running Craft Pro with a Craft Solo license. Please fix on an environment where administrative changes are allowed.
  * 3 plugins have licensing issues. Please fix on an environment where administrative changes are allowed.
  </code></pre>
  <p>Fair enough. I logged in to my local environment, and licensed the CMS as well as the plugins. This triggered a change to project.yaml and I can see the addition of the licenses. I then pulled to my production environment, synced changes, and I expected to see these warnings disappear. However, the warnings are still there.</p>
  <p>Any suggestions as to what I'm doing wrong here?</p>
  <p>====
  UPDATE</p>
  <p>Brad's answer below resolves the issue, but there's one additional note. There are many caches in the CMS &gt; Utilities &gt; Clear Caches. The cache that stores licensing is &quot;Data caches&quot;.</p>
  
Tags: <license><project.yaml>
Title: Craft and Plugins are licensed, but I'm still seeing warnings on Production
ThreadText: # Craft and Plugins are licensed, but I'm still seeing warnings on Production
  
  (Asked by: username_0 on 2020-06-17)
  
  In my production environment, I have administrative changes disabled, so I see the following messages:
  
  ```
  * You’re running Craft Pro with a Craft Solo license. Please fix on an environment where administrative changes are allowed.
  * 3 plugins have licensing issues. Please fix on an environment where administrative changes are allowed.
  
  ```
  
  Fair enough. I logged in to my local environment, and licensed the CMS as well as the plugins. This triggered a change to project.yaml and I can see the addition of the licenses. I then pulled to my production environment, synced changes, and I expected to see these warnings disappear. However, the warnings are still there.
  
  Any suggestions as to what I'm doing wrong here?
  
  ====
  UPDATE
  
  username_1's answer below resolves the issue, but there's one additional note. There are many caches in the CMS > Utilities > Clear Caches. The cache that stores licensing is "Data caches".
  
  **Tags:** license, project.yaml
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-06-17. Score: 1 | Accepted answer
  
  You probably just need to clear the Craft `storage/cache` folder on production.
  
  Licensing info is cached for 24 hours at a time.
  
  > **Comments:**
  > **username_0**: This is a good rule of thumb which I completely blanked on yesterday. Thank you sir.  
  
  ---
  
  