Every time I launch the native Figma app on macOS (macOS 13 Ventura) I get this notification:
Login Item Added: "FigmaAgent.app" will open automatically when you log in. You can manage this in Login Items Settings.
And following the instructions on the notification I can remove the Login Item as expected, but I will get the notification again next time I launch the app, and the Login Item will be added once more.
I want to remove it and never to be added again.
How can I do that?
Pd: I reached out to Figma support a few times, and they mostly ignored my messages, and when I asked why was I being ignored they gave me a rather unhelpful answer:
Hey there, sorry for the delay & confusion. We didn't reply, because the answer was in your original tweet. Sorry if it wasn't obvious, but in the screenshot, you manage it from Login Items Settings: Apple menu > System Settings, click General in the sidebar, then Login Items.
To be very clear, I don't want to know how to remove FigmaAgent from Login Items, I want to know how to prevent it for being added again.
From https://twitter.com/qdoug/status/1374785043504185351:
This seems to work for removing FigmaAgent:
Force Quit it in Activity Monitor
Remove it in System Preferences -> Users & Groups -> Login Items
Delete ~/Library/Application Support/Figma/FigmaAgent.app
Delete /Applications/Figma.app/Contents/Library/FigmaAgent.app
Related
I'm at a total loss here and have nowhere to turn.
I made an app, set a name as Test App. Working fine. Update the name under Display Information to Dashboard App. Then I click Install your app to your workplace and authorize it.
And... nothing.
I've restarted slack. I've waited now 8 hours. I've tried again. I changed the Bot name itself. Yet the thing still says Test App
Found a different solution that updated immediately, which I had to do AFTER I did what was described by #plowman, to have the changes reflected in Slack:
Right click on bot name on Slack> Open App Details
In pop up, click Configuration, will redirect to browser tab
In browser, scroll down to Bot User section, find edit button
Change name and save
To edit the app name after it has been installed, you have to find the app in the "App Directory" for your Slack workspace.
First, open Slack, tap on the workspace name ("Raikes" in this case), tap "Settings & Administration", then "Manage Apps":
Next, scroll down to "Bot User" and edit the bot name to be whatever you want:
In the process of writing this I figured it out.
While you can rename the bot and save, this apparently does nothing. You must delete the bot and add it again, then reinstall the app. This creates a new auth token and bot ID, which you must also update in your app.
Only then will the name change.
previous answers only change the name of the bot in charge of acting on behalf of the app. If you want to change the name of the app itself, you could:
you gotta go to https://api.slack.com/apps
then check the app lists shown
select the app you want and go to the "Display Information" section
update the app name
in the end, click on the "save changes" bottom.
As you all know, Apple changed how Xcode works such that you can't ever create an app with a previously used app ID, even if you're just writing test apps to use locally. Up until now I've just been typing in garbage IDs to get around this stupid antifeature, but today I was greeted with this gem:
So now I'm blocked from creating any more test apps, effectively stopping my development dead in its tracks (I write libraries and frameworks, and need to test them in test apps).
Does anyone know of a way to bypass or disable Apple's restrictions?
It is a kind of limit of free developer accounts, but you could figure out a solution for that:
1- Navigate to the project of any previous application that have been installed on the same device has the problem with .
2- Open Build Settings tab for the app project in Xcode .
3- Search for Bundle ID and copy it .
4- Open up your current app that has the problem and navigate to the same place > Paste and Replace the current Bundle ID with the old one.
5- Run the app.
!!! WALA
Same thing happened to me. I presume it's some kind of a new limit that Apple has put on "non-paying" developers, and that it limits you to 10 apps in 7 days.
Edit - To resolve this, I'll just make a random apple dev ID...
I faced the same situation in my new mackbook with xcode 7.3.1 version.
Even if I tried with old bundle identifier, it didnt worked.
Following below steps helped me to run the app in device.
Got to xcode preference
Click accounts and choose your apple id.
Click the View details
And Click download All.
This will download all the provisioning profile associated with given apple id.
And after that use any identifier that you have used before. You can easily get the old identifier from provisioning profile names.
Just use the bundle ID of any old app that you have already installed like this and change the bundle ID after 7 days. I think apple puts a limit for free developer accounts.
EDIT:
Its important about what #haquangvu mentioned in his answer that, your old app get replaced. So take care of it and thanks #haquangvu for your answer.
Use one of your old Bundle IDs.
It works.
But your old Application will be delete.
DO NOT MAKE ANOTHER ID thats not the solution!!!
To make it work thats what you need to do:
Window > Preferences - Account
Then choose your apple ID and your team, then click on View Detail... Button on the bottom right.
A new window will show up, click on Download all button on the bottom left and all of yours Provisioning Profile will show up.
After that just Left click on those ones you don't have to use anymore and click to move to trash.
after you delete enough profiles, you'll be able to build your project again!
I had this and the other answers here didn't fix the problem. I solved it by opening Window > Devices, finding my device, right-clicking it to "Show Provisioning Profiles", and then deleting a bunch of the profiles there.
Then it worked!
The workaround is to use an id that you previously created. As Xcode does not list the Bundle IDs via Apple ID Details any more, save this into your .bash_profile or ~/.zshrc and call it with list_xcode_provisioning_profile from a terminal
list_xcode_provisioning_profiles() {
while IFS= read -rd '' f; do
2> /dev/null /usr/libexec/PlistBuddy -c 'Print :Entitlements:application-identifier' /dev/stdin \
<<< $(security cms -D -i "$f")
done < <(find "$HOME/Library/MobileDevice/Provisioning Profiles" -name '*.mobileprovision' -print0)
}
To make this answer easier to find I just copied it from hyperknot here: Parsing mobileprovision files in bash?
I have a paid developer account and found this happening in Xcode 9 after creating a bunch of simple test/example apps. In the past, I would have simply selected a "wildcard" App ID. However, Xcode doesn't seem to have a way to do this anymore.
Researching based on the wildcard, I found Technical Q&A QA1713: When should I use a wildcard App ID?. Following these steps seems to have worked for me. (The signing errors are gone, but we'll see what happens in another 7 days or 10 apps, lol.)
Here are the steps, if you have a paid developer account:
Log into your developer account.
In the list on the left, click on Certificates, Profiles & IDs.
In the new list on the left, under Identifiers, click on App IDs.
Click the '+' symbol in the upper right of the page. (You're now at the 'Registering an App ID' page.)
In the box under App ID Description, enter something to describe your App ID. (Note that this description has to be purely alphanumeric; spaces seem to be allowed, but nothing else.)
Under App ID Suffix, select the radio button for Wildcard App ID.
In the box below that, enter the beginning of what you'd like to use as your app's bundle identifier, followed by a dot-asterisk. (For example, maybe your app bundle identifiers in Xcode are something like com.myname.appname. Then, in the box under Wildcard App ID, you'd enter com.myname.*.)
Under App Services, select any available items you think you might use in an app at some point in the near future. (Only a few of the items are available for selecting at this step.)
At the bottom of the page, click the Continue button.
At the resulting 'Confirm your App ID.' page, scan your selections to ensure they're okay; then, at the bottom of the page, click the Register button.
At the resulting 'Registration complete.' page, you can again review the registered options. Then, just scroll to the bottom, and click the Done button.
The new wildcard App ID will now appear in your list of App IDs.
Next, go into Xcode, and create your app, entering an Organization Identifier that matches the wildcard App ID you registered without the dot-asterisk. (For example, if you enter com.myname, Xcode completes what becomes the bundle identifier with a dot and the app name.)
When the project opens at the signing page, Xcode will "Automagically manage signing" correctly ;)
Note: If you have a free developer account, as of the date of this posting, you can't access the 'Certificates, Profiles & IDs' link in your account. ;(
Xcode>General>Identity
Copy Previous Bundle ID
Bundle Identifier : AppleDeveloperName-PreviousProjectName(or whatever)
Paste it in the new project's Bundle ID. It should be fine now.
Can someone clarify how do I create an update in the Windows Phone Store? I'm confused on how to get this to work.
In the lifecycle section, I've got the option to "add a new file" or replace the existing one.
If I select "add a new" file, I need to re-specify all the information for the file all over again i.e. version, keywords, description, changes, etc...
If I select "replace" file, it does just that but I don't get notified that an update is available and when I go to the store, it doesn't give me the option to update, which means that I first have to uninstall the app and then install it again.
What am I missing?
Thanks.
Basically, say if you already have a WP8 app in store, and you are adding a WP8.1 version, You need to choose add new to upload the new appx file to store.
If you simply want to update your existing WP8 xap, you need to select replace instead.
When you are done with the change, click the Save button at the bottom of the page. And after you will need to click Review and Submit, followed by a final Submit button.
After all this, you will need to wait for Microsoft to send you an email saying either it's certified or rejected. They used to send out an email right after you submitted something, they don't do it anymore.
The good thing is that the certification process now takes much less time than before. I just submitted my last update and it got certified within 15 minutes.
I'm new into this.. trying to create a simple app for macosx, basically I want this app to startup right after the user login with username/password..
and it's just a simple app has a window & that window displays a warning message and then have two buttons "agree" & "decline"
if the user hit agree then it will continue to the login process.. works as "LOG IN button"
if the user hit Decline then it will go back to the loginwindow..works like "CANCEL button"
but since am new into Xcode.. I have already created the app with both buttons.. but don't know how to add IBAction and Outlets!..
Any ideas?..
Thanks
This should give you an idea. Also, since you are new to ios/mac dev, I would suggest you to read the documents from Apple that will provide you with a wealth of information. Additionally, read the FAQ of the site to get a better understanding how SO functions.
I'm currently developing a wp7 app (don't want to tell too much ;), but I'm struggling a little with the user interaction.
The main question, I'm not sure about is: Should I offer an explicit save button in dialogs and use the phone back button as cancel, or should I save implicit the time the user taps the phone back button ...
The more I think about, the more I'm unsure about the best user experience.
I already read the user experience and interaction guide from Microsoft, but there isn't any advice in there about that issue ...
Thx alot for your suggestions.
On page 68 of the Windows Phone 7 UI Design and Interaction Guide it states:
Changes to Application Settings should be immediately implemented. This means that a "Done", "OK", or other confirming dialog is not neededd. In some cases, even though the change has happened immediately, the user may not have feedback that the change has occurred until an ongoing event is completed or a future event occurs. Examples would be joining a secure Wi-Fi network or changing the frequency of alarms.
Keeping Application Settings brief and clear should be a design goal. Complex, multi-page, multi-level Application Settings can frustrate or confuse users into thinking that they have entered another application entirely.
Although the same page also goes on to say:
Immediately implement user-selected Application Settings without a confirming dialog box and provide a feedback method to indicate that the change has occurred.
Avoid creating Application Settings that have more than 2 pages (screens). Settings that require more than a single screen should use overlying half screens to avoid losing context when
the SIP Keyboard is displayed.
If a task cannot be undone, always provide the user with an option to cancel. Text entry is an example. Actions that overwrite or delete data, or are irreversable must have a “Cancel” button.
When using additional screens with commit and cancel buttons, clicking those buttons should perform the associated action and return the user to the main settings screen.
To keep the heading of settings control panels consistent, the heading for the settings page should look as follows:
SETTINGS
<CPL Name/ Application Name>
Applications that fetch data over the network must have an option to disable data usage.
So, I think you only get in to questions over explicit vs. implicit if you have multiple pages for settings, and if you do it sounds like the explicit would be the way to go with sub-pages, but implicit for the initial page.
You should use explicit saving of settings.
However, for data entered it will depend on the application and the data being entered.
It's typcial to include a save button (or equivalent) otherwise there's (probably) no way for the user to cancel out of a partially entered form. This can also cause issues if there are validation issues which would prevent the saving of the partially entered data.
It depends on the app though. There is no universal rule for this.