As titled, I changed the date of my computer system to 2038/1/1
for something else, and then I resume to 2016, however the profile in my Xcode 8 is expired on 2017/10/24 that is the system date is still 2038/1/1 as the photo shows below.
The question is how can I solve it? Thank you.
Go to apple member center, check if that specific provision profile shows as valid or expired. I assume it will be valid, if so, delete that provision profile from your mac and re-download it from the member center. Inc case the provision profile is expired also in member center, then you will need to generate a new one...
Related
I wrote an app script which provides a web UI for data entry into a team calendar. I published it using G-Suite super admin account and added it as Trusted App under Security/API Permissions. "Trust domain owned apps" is checked under "Internal App Settings".
When a G-Suite user in our organization tries to access the app, he sees
"The developer of ShiftSchedulingApp, admin#_our_organization_.org, needs your permission to access your data on Google."
Those brave enough to click "Review Permissions" are taken to the next message:
"ShiftSchedulingApp wants to access your Google Account. See, edit, share, and permanently delete all the calendars you can access using Google Calendar"
Of course nobody wants to risk losing all the calendars on their Google Account and this is where it ends.
How do I get rid of this misleading message? It's not Google account, it's their organization account on G-Suite. It's not all their calendars, it's the shared team calendar only. It's adding data, not permanently deleting calendars. It's published by their administrator in their G-Suite, not an unknown 3rd party.
I spent days trying to make this message go away but no luck. App must be executed as an accessing user and not as publishing user because their user ID determines what shifts they can fill on a calendar.
I'd appreciate any hints pointing me the right direction.
I experimented with variations of the two-app approach as suggested.
The app which provides the UI needs to read the calendar to display available shifts - so I can't get away from the user authorization prompt.
Another variation I tried was having one app do everything and run as me, and another do nothing but return Session.getActiveUser(). I tried calling the 2nd one from the 1st one on the client side via XMLHttpRequest. It would be ideal for my needs - but I hit CORS error as apps URL is script.google.com but it actually gets redirected to script.googleusercontent.com. There doesn't seem to be a way to set CORS in Google App Script.
Although I was not able to find a way to avoid prompting users for authorization when executing the app as accessing user, it turns out my reasons for doing that were based on a false premise.
I chose to publish app as accessing user because I thought that's the only way to get accessing user Id - which is true for non-G Suite accounts.
However, when app is published by a G Suite account, the app can get accessing user ids within the same G Suite domain even when it's set to execute as publishing user.
Thanks Niek and TheMaster for your help!
If you just need user ID, why do you ask for all those permissions?
Possible Solutions:
2 web-apps- One running as you and another as user accessing (with only profile) permission. The second one will be the actual web interface and POST necessary information to the first one with privileges. OR
Implement your own web-app Google-sign in1
Use the least permissive2 scope3
I am trying to login to my heroku account.
I keep getting an error message that says "There was a problem with your login". There are no details of what the problem is.
I tried changing my password through the forgot password action and I still get directed back around to the above error message.
I can't contact Heroku's support team because I can't login.
Has anyone found this problem and found a way around it - or even a way to contact Heroku?
I had the same problem, couldn't login even after resetting my password. I use the Last Pass chrome extension to fill in forms. When I entered the (same) credentials in manually I was able to login.
I started getting this error very recently. I believe it's linked to a recent email that I got regarding password requirement changes:
Heroku will start resetting user account passwords today, May 4, 2022, as mentioned in our previous notification. We recommend that you reset your user account password in advance here and follow the best practices below:
Minimum of 16 characters
Minimum complexity of 3 out of 4: Uppercase, Lowercase, Numeric, Symbol
Don't just add a letter or a 1 digit number to the existing password while changing
Passwords may not be duplicated across accounts
As mentioned elsewhere, resetting my password and ensuring LastPass included symbols resolved it.
I reset my password and it helped.
After a research I found that Last Pass auto generated password was not strong enough as per Heroku password reset requirement.
I solved it by opening password reset link on different browser (in my case safari). enter strong password (ex: 51lxgpf2F52PgOBAPdAM#)
I had this problem on "Opera", then I went to "Chrome", and still the error, but in the end it worked on "Microsoft Edge". So try changing your browser to this one)
I have one account which I am closing (http://www.facebook.com/UrbanDystopia - email address: urban#urbandystopia.com) and I have already opened another under my name (http://www.facebook.com/david.manning.336333 - email addresses: davem#roseandmoon.com and david.manning.336333#facebook.com).
I am closing http://www.facebook.com/UrbanDystopia and I am the administrator of two apps - Bbblackdog (266537753438090) and CanCon (385773268120508) - therefore I "must either delete or transfer ownership of them before deactivating".
I want to transfer the ownership of both of them to my new account, but when I attempt to add a new admistrator to either one of them, I get this: "davem#roseandmoon.com is not a Facebook user" and also "david.manning.336333#facebook.com is not a Facebook user" and also "david.manning.336333 is not a Facebook user".
It won't let me add my new account, which does exist and those are the e-mail addresses to the new account.
As there is nowhere one can e-mail Facebook anymore to ask for help, I came here as a last resort after reading everything on Facebook about apps I could, none of which answered this question.
Can anyone please assist?
Dave M.
It seems that your problem is related to this issue
Creating A New App For Page
Just like your new account is not verified.
I have requirement to show status (locked or unlocked ) of all accounts in OpenDS 2.2.
I have come to know that pwdAccountLockedTime is present if account gets locked due to too many unsuccessful attempts. So by checking this attribute, I am able to pick account locked due to this reason.
Now I need to identify accounts which were locked due to password expiration. Is there any attribute which tells this?
I need to retrieve this attribute in my java client application.
Any help in this regards would be greatly appreciated.
P.S. - I have checked other threads and forums but none of the solutions given seem to be working - like checking pwdLockedTime (I could not find this attribute).
You can check the status of an account and get details of locked account using the manage-account utility.
When the password has expired, there is no marker that it's locked. The server uses the pwdChangedTime and the currentTime to see if the difference exceeds the expiration time.
Kind regards,
Ludovic.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Code Sign error: Certificate identity 'iPhone Developer: My Name (xxx)' appears more than once in the keychain
We have two different Developer accounts (one for store and one for enterprise). The enterprise account came later. Long Story
They are administered under two different email/accounts.
I am trying to allow one XCode project with two different targets to sign our app for either of the accounts based on whether im doing a store or enterprise build. The problem is I get the error message from the title.
They are separate certificates with different private keys so I dont understand why they cant coexist and why XCode cant tell them apart.
IS there any way I can have two different targets in XCode with these different certs/provision profiles?
Update: Per my comment i was able to sign the app for either target, but now when i got to produce an IPA, i get an error about ambiguous certificates from the two different keychains.
Thanks!
Here is what worked for me on Lion ver. 10.7.3 with XCode 4.3.1, and a lot less painful than rolling back to 4.2!
In Keychain Access, make sure your "View" menu > Show Expired Certificates option is turned ON.
Click the "Certificates" 'Category' and then click through every one of the keychains you have listed in your 'Keychain' sidebar in Keychain Access. If you see any duplicates, even expired certificates, delete those duplicates.
Click the "Keys" 'Category' in Keychain Access.
Navigate through every keychain looking for and deleting any "Orphaned Keys" that have the same Common Name as the affected certificate. Orphaned keys are ones that are not bound by a Disclosure Triangle to an iPhone Developer or iPhone Distribution certificate that currently exists in the keychain.
If you found and removed any extra keys or certificates, then re-attempt your build.
This worked for me after this point - but including the parts below from Apple in case it doesn't work for you.
If the issue persists after removing all active or expired duplicate certificates or keys by the same common name, you might try removing all existing signing certificates and keys and replace them with new ones using the steps in How do I delete/revoke my certificates and start over fresh?.
Finally, if the error persists even after creating new certificates, please control-click on the affected certificate in Keychain Access, choose "New Identity Preference" and click the 'Certificate' field.
If you see duplicate certificates listed in here, this is an known and uncommon issue with Keychain Access.
To work around the problem, try the following:
Export your developer profile using the process in Transferring Your Identities.
Create a new OS X User Account, install Xcode for the new user and import the developer profile created in the previous step.
The same issue for me. After renew the certificates (Development and Distribution)
To solve it go to the keychain tool and follow the next steps
View --> Show expired certificates
Select KeyChain System
Select Category All items
You should see some certificates expired, just remove it and rebuild.
hopefully helps