Skip to content
View in the app

A better way to browse. Learn more.

Tip.It Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SwiftKit not working

Featured Replies

5502f35d690a3-Screenshot_62.png

Sometimes I like to dig a hole in the ground and pretend I'm a carrot.

userbar_350.gif

  • Author

Can't find that file.

5502f35d690a3-Screenshot_62.png

Sometimes I like to dig a hole in the ground and pretend I'm a carrot.

userbar_350.gif

  • Author

Had to reboot, sorry.

5502f35d690a3-Screenshot_62.png

Sometimes I like to dig a hole in the ground and pretend I'm a carrot.

userbar_350.gif

Make sure you install and run SwiftKit as an administrator (Right click > Run as Administrator)

  • Author

I do/did?

5502f35d690a3-Screenshot_62.png

Sometimes I like to dig a hole in the ground and pretend I'm a carrot.

userbar_350.gif

Then we really need the debug data from the file, if it's not being written there's something inherently wrong with your system beyond the support we provide I'm afraid.

Then we really need the debug data from the file, if it's not being written there's something inherently wrong with your system beyond the support we provide I'm afraid.

I might be able to suggest a workaround for their issue, even though it's a bit off-the-wall.  They'll just have to re-permission the directory that SwiftKit is installed in with...

 

SYSTEM - Full Control

Administrators - Full Control

Everyone - Full Control

 

...make sure it trickles into all the subdirectories/files of that directory area only, and that should give SwiftKit a fair chance to either update or spit back a Debug Information file.  Which brings me to ask, why don't you just preset permissions similar to these when the program is first installed? :(

 

~D. V. "seeing one too many of this type of thread created" Devnull

tifuserbar-dsavi_x4.jpg and normally with a cool mind.

(Warning: This user can be VERY confusing to some people... And talks in 3rd person for the timebeing due to how insane they are... Sometimes even to themself.)

We don't force permissions because it's inherently insecure and circumverts the security processes in place by AUC in the first place.

 

We want to be advocates of good security practices as well as provide a great tool after all :)

Hmm... That's understandable.  I don't like to sacrifice security, provided that can be avoided, as well. :-k

 

There's got to be some way, however, to dodge making people have to "Run As Admin" as many times as there have been?  Doing so creates an even larger dangerous exploit, as the program scope and permissions (at least as I understand them from having been a WinXP user for some time) become unconfined from the User Account that it's running on. :?

 

Could you (or someone else in the SwiftKit team) perhaps design a system service program that only your application could connect with, would only run while your application is up, but could handle the updating work?  Maybe then like Valve's Steam client (which kind of gave me this idea, but I'm thinking a little less aggressively), then the critical part that hits all these errors might be able to do its' job, but without having to open up the main program in Admin mode. :huh:

 

~D. V. "Trying to think of a way to help end the problem..." Devnull

tifuserbar-dsavi_x4.jpg and normally with a cool mind.

(Warning: This user can be VERY confusing to some people... And talks in 3rd person for the timebeing due to how insane they are... Sometimes even to themself.)

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.