If I understand you correctly, this isn’t an issue. It’s by design. From the SEO Framework description here on the plugin repository:
The SEO Framework will automatically deactivate its Sitemap functionality when another (known) sitemap plugin is found.
Since Jetpack inserts its sitemap, TSF automatically deactivates its sitemap to avoid confusing search engines.
@hubmacfan Thank you so much for helping out 🙂 You understood correctly, but this is an odd case.
Jetpack isn’t one of the plugins detected, as it covers so many features independently. We do know how to detect the activity of their sitemap’s functionality, but it has yet to be completely embedded in the plugin. But I digress.
The sitemaps are outputted on the same endpoint (/sitemap.xml). So, the sitemap that’s first to register will be the one used.
@wpzones
If you disable the sitemap functionality via Jetpack (under “Traffic”), and re-save the SEO settings of The SEO Framework, the sitemap of TSF should appear.
If you can’t disable the sitemap functionality in Jetpack, please reach out to their support team. It is probably a JavaScript issue, so you might wish to state your browser version.