Xcode 7: App installation failed: A valid provisioning profile for this executable was not found

I have already searched and almost implemented max solution but it's not installing any app even though if I am creating just sample single view app.

App installation failed
A valid provisioning profile for this executable was not found.

============== update ====================
I fixed this issue today.
First, go to ~/Library/MobileDevice/Provisioning Profiles. Make sure Xcode isn't running. Then, delete all provisioning files (like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision).
Start Xcode.
You will see something like "Fix this issue" in your Target's General tab. Click it.
Xcode will now load new provisioning profile.
That's it.

----------- OLD Answer -------------

I have same problem now.
I've checked my provisioning profile using https://github.com/chockenberry/Provisioning/releases.
In my case, my provisioning profile had the wrong UDIDs but right machine count.
I've registered machines, and Apple Developer Center listed right UDIDs for those machines.
However, whenever I downloaded new provisioning profile, it contained wrong UDIDs.
I think Apple's system is outputting wrong provisioning profile.
I called Apple support for this issue today, but Apple only emailed me with their knowledge base links(forums,documents,etc).

Possibly you are using App Store distribution provisioning profile. Use development or Ad-Hoc provisioning profile.

For Xcode 8 / Swift 3.0 In my case, for my app target and my extension in "General" I check "Automatically manage signing" and it work

I was having this issue because the date/time on my iPhone was not the same as that on my Mac running Xcode ( i changed the date on my iPhone while testing some app). On my iPhone, i went to Settings > General > Date & Time > Set Automatically

This fixed it

Make sure you have added device UDID in your provisioning profile.

• Go to provisioning portal.
• Edit provisioning profile.
• Make sure device is checked.
• Done, download
• Use new Profile

Another possible reason: Device date is set to later than the expiry of you provisioning profile.This is very weird but, it could happen.