Skip to content

japlscript/obstspot

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

LGPL 2.1 Maven Central Build and Test

Obstspot

Obstspot is a Java API for the Spotify app (macOS) based on JaplScript.

Installation

Obstspot is released via Maven. You can install it via the following dependency:

<dependency>
    <groupId>com.tagtraum</groupId>
    <artifactId>obstspot</artifactId>
</dependency>

The Maven artifacts also contain sources and javadocs.

If you are using modules, its name is tagtraum.obstspot.

Usage

To use the generated code, do something like this:

import com.tagtraum.macos.spotify.Application;

public class GetCurrentTrack {

    public static void main(final String[] args) {
        final Application application = Application.getInstance();
        final Track currentTrack = application.getCurrentTrack();
        if (currentTrack == null) {
            System.out.println("No current track");
        } else {
            System.out.println("Current track: " + currentTrack.getName()
                + " by " + currentTrack.getArtist());
        }
    }
}

Or this:

import com.tagtraum.macos.spotify.Application;

public class PlayTrack {

    public static void main(final String[] args) {
        // provide URI, like "spotify:track:5Up9Lj7QWudEfMc0ve5qWW"
        // as parameter
        final String trackURI = args[0];
        final Application application = Application.getInstance();
        // arguments to playTrack are: trackURI and contextURI
        // contextURI (this is the album or playlist URI) is optional,
        // just leave it "null", if unknown.
        application.playTrack(trackURI, null);
    }
}

API

You can find the complete API here.

AppleScript Sandbox

Since macOS 10.14 (Mojave), Apple imposed a sandbox on AppleScript. Therefore you may see dialog boxes requesting authorization to perform certain actions. After a while, these boxes simply disappear and there does not seem to be an easy way to authorize your app. In this case, you need to open the system preferences, navigate to Security & Privacy, Privacy, and then Automation, and make sure your app is allowed to remote control whatever app you are trying to remote control (see also this article).

If you are shipping a real app with a UI and not just a command line tool, you need to customize the sandbox permission dialog. You can do so by adding the key NSAppleEventsUsageDescription to your app bundle's /Contents/Info.plist file. For example:

[...]
<key>NSAppleEventsUsageDescription</key>
<string>SuperMusic uses AppleEvents to access your Music.app library,
        e.g., to set BPM values or create playlists.</string>
[...]

Apple's documentation for the keyword is here.