Feature with a View does not install the View

Did you find any solution to this? I am having the same problem with a simple view using content type and taxonomy. It is actually installed, I can see the views_view table, but it does not appear in the UI and is not accessible in any way.

Thank you

Same problem here, though I can't see the Views in the views_view table (no matter how many times I clear all caches and disable>uninstall>enable the Feature...). I think last time I came across this problem I ended up not using Features to manage default Views, but I really *want* it to work. Will try some debugging. I'm using the latest 6.x-1.x-dev version (from 2011-10-23).

Hmm, found the cause of the problem for me, and it's a silly one (though could easily happen to others):

The Feature/module I'm working on has custom functions in the .module file, and I'd recreated the Feature several times (which maintains any custom code in the .module file), and inadvertently removed the include for the .features.inc file that normally goes at the top, without having copied the contents of that file (just an implementation of hook_views_api) into the main .module file. Oops.

Also happens to me on D7: every components get created except the view.
I found that it will appear with some feature-revert/clear-cache but only if there is absolutely no component already overriden. Otherwise the view never appear.
[ on the new site I want to use the feature, there is some component (node/user permission) that are always overriden so the view component will probably never appear ]
[edit] Finally I can't say for sure that my featurized view ever worked (it may have been the DB it was created from).
Hopefully mysqldump db view_views view_display did the trick.

The view should never appear in views table on a fresh install of a new feature. It only ever appears on overriding a view or creating a new one; i.e. it's a true exportable and remains in code unless overridden.

Make sure the features.inc is included at the top of .module and that hook_views_api is included in it, and that the view was exported to mymodule.views_default.inc. Past that, it's views territory.

Marking as fixed for now as seems like user error.

mymodule_views_api is defined in mymodule.features.inc
mymodule.views_default.inc includes the views
But the .module is blank and does not include mymodule.features.inc (D7.x, features 7.x-1.x in my case).

That'd be the problem. do you recall doing anything that would result in a blank .module? I think features throws a warning when the .module is lacking (there's a few issues already to improve this)

I was maybe misleading, the file is not blank but rather useless:

<?php
/**
 * @file
 */

// Drupal needs this blank file.

The first time I used features and saw this file, I thought it was expected...
But I'm probably commenting on a the wrong issue, still I don't really know how buggy is this behavior and
where to comment/test.