name: TensorFlow Lite in Play Services issue
about: Use this template for issues with TensorFlow Lite in Google Play Services
labels: 'comp:lite-in-play-services'

---

**System information**
- Android Device information (use `adb shell getprop ro.build.fingerprint`
  if possible):
- TensorFlow Lite in Play Services SDK version (found in `build.gradle`):
- Google Play Services version
  (`Settings` > `Apps` > `Google Play Services` > `App details`):

  public ServiceManager startAsync() {
    for (Service service : services) {
      checkState(service.state() == NEW, "Not all services are NEW, cannot start %s", this);
    }
    for (Service service : services) {
      try {
        state.tryStartTiming(service);
        service.startAsync();
      } catch (IllegalStateException e) {
        // This can happen if the service has already been started or stopped (e.g. by another

        }
        this.service0 = this.service;
        this.connectionState = 0;
    }

    boolean matches(final String share, final String service) {
        return this.share.equalsIgnoreCase(share)
                && (service == null || service.startsWith("??") || this.service.equalsIgnoreCase(service));
    }

    @Override
    public boolean equals(final Object obj) {
        if (obj instanceof final SmbTree tree) {

    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "base-services",
    "path": "platforms/core-runtime/base-services",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "base-services-groovy",
    "path": "platforms/core-configuration/base-services-groovy",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false

        }
      },
      {
        "subprojects": [
          "base-services",
          "flow-services",
          "input-tracking",
          "internal-integ-testing",
          "jvm-services",
          "messaging",
          "persistent-cache",
          "plugins-java",
          "problems",
          "process-memory-services",
          "testing-base-infrastructure"
        ],

Matsutani Kenji <******@****.***> 1477575947 +0900

 * to the Maven build process.
 * <p>
 * SPI services are typically registered in {@code META-INF/services/} files corresponding to
 * the specific service interface being implemented.
 * <p>
 * All SPI services should be annotated with {@link Consumer} to indicate they are meant to be
 * implemented by plugins and extensions rather than used by them.
 *
 * @since 4.0.0
 */
@Experimental
@Consumer

 *     <li>{@linkplain org.apache.maven.api.services.ProjectManager#attachArtifact(Session, Project, Path) artifacts to be attached to a project}</li>
 * </ul>
 *
 * <p>For the main artifact and attached artifacts, the
 * {@link org.apache.maven.api.services.ArtifactManager ArtifactManager} service must be used
 * to point the artifact to a {@link Path} during the packaging phase.</p>
 *

import org.apache.maven.api.Service;
import org.apache.maven.api.Session;
import org.apache.maven.api.cli.extensions.CoreExtension;
import org.apache.maven.api.model.Plugin;
import org.apache.maven.api.services.ArtifactCoordinatesFactory;
import org.apache.maven.api.services.ArtifactManager;
import org.apache.maven.api.services.ArtifactResolver;
import org.apache.maven.api.services.Interpolator;

    SmbTreeImpl(final SmbSessionImpl session, final String share, final String service) {
        this.session = session.acquire();
        this.share = share.toUpperCase();
        if (service != null && !service.startsWith("??")) {
            this.service = service;
        }
        this.service0 = this.service;

        this.traceResource = this.session.getConfig().isTraceResourceUsage();