Invalid Toolchain Xcode 7 Upload Issues

Hi there,
Yesterday everything was working fine and we was updating our Apps on iTunes Store, but today we have some issues with it.
Done some research of it and did not find anything helpful.

After Uploading to iTunes through Xcode Uploader we get email:
Dear developer,
We have discovered one or more issues with your recent delivery for . Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Invalid Toolchain - New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, macOS, and iOS SDK. Don't submit apps built with beta software including beta macOS builds.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.
Regards,
The App Store team


We using:

• Xcode7.3.1 (7D1014)
• OS X El Capitan Version 10.1.6

And after pressing Submit For Review Button in come up this message

New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, macOS, and iOS SDK. Don't submit apps built with beta software including beta macOS builds.


Also after uploading process was finish we also receive this email:
Dear ,
The following build has completed processing:
Platform: iOS
App Name:
Build Number: 1.3.1
Version Number: 1.3.1
App SKU:
App Apple ID:
You can now use this build for TestFlight testing or submit it to the App Store.
If you have any questions regarding your app, click Contact Us in iTunes Connect.
Regards,
The App Store team

if someone know anything we would really appreciate all assistance.

Thank to all.

 

Sounds like an issue on Apples side. Might need to hold tight for few days for Apple to sort things out. Similar issues seem to happen every year around this time due to the pending major updates of Xcode / iOS / macOS.

 

Thank you @Andy ,
We was also thinking about that.
Really appreciate your time to go threw our message and reply.

 

Hi @Andy
Just an update.
Today we try to Submit our game for Review and it worked without issues.
So it was something on their side, and now is fixed.