I've been having an issue since 22/01 where I can't see the latest changes to my PCF control, even though both npm run build and pac pcf push complete successfully in the Developer Command Prompt and confirm the control exists. Around that date, we changed the constructor name from SchedulerProPCFNew to DualSchedulerPCF to avoid confusion, as the display-name-key and description-key were also named SchedulerProPCFNew. This update was made in index.ts, ControlManifest.Input.xml, and the generated ControlManifest.xml. However, the component still builds and pushes without any errors which confuses me as to why it doesn't appear in the code components section.
Knowing that Power Apps identifies a control through the combination of namespace, constructor, and version, I am concerned whether this identity change might cause the platform to treat the updated control as a different component. As a workaround to this issue I implemented 3 ways to get the control to reflect but none of them have worked unfortunately. Seeing as the problem is when I changed SchedulerProPCFNew to DualSchedulerPCF, Power Apps now sees the old control as Sygma.SchedulerProPCFNew (last updated Jan 22) and the New control as Sygma.DualSchedulerPCF (exits but potentially hidden by display name).
- For the first work around, I made the new control visible by making its identity clear. Incrementing the version, updating its display-name-key (to match constructor - DualSchedulerPCF ) and description-key (Dual Scheduler Component v2). Build and push and check power apps code component. The last push still registers as the 22nd of Jan.
- I then attempted a quick fix by reverting the control to its original name, SchedulerProPCFNew, which should technically work without any data binding. However, despite building and running successfully on the CLI, it still didn't appear in the code components.
- Lastly, I tried using the new constructor (DualSchedulerPCF) while keeping the old display names to trick Power Apps into recognising it as an update to the existing control. Unfortunately, this approach also failed. It's quite frustrating because without the latest code component, I can't see any new updates to my app.
Thanking you in advance for all your help and support so far 
