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

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

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.

    "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

 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.job;

import org.codelibs.fess.app.service.CrawlingInfoService;
import org.codelibs.fess.app.service.JobLogService;
import org.codelibs.fess.app.service.SearchLogService;
import org.codelibs.fess.app.service.UserInfoService;
import org.codelibs.fess.helper.SystemHelper;
import org.codelibs.fess.mylasta.direction.FessConfig;

 * 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

            <option value="$PROJECT_DIR$/platforms/core-runtime/process-memory-services" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/process-services" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/process-services-api" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/process-services-base" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/report-rendering" />

  }

  private static void assertState(
      ServiceManager manager, Service.State state, Service... services) {
    Collection<Service> managerServices = manager.servicesByState().get(state);
    for (Service service : services) {
      assertEquals(service.toString(), state, service.state());

import org.apache.maven.api.annotations.ThreadSafe;

/**
 * Marker interface for all services provided by the {@link Session}.
 * <p>
 * Services can be retrieved from the session using the
 * {@link Session#getService(Class)} method.
 *
 * @since 4.0.0
 * @see Session#getService(Class)
 */
@Experimental
@ThreadSafe